> ## Documentation Index
> Fetch the complete documentation index at: https://docs.codeobsess.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Your first ticket

> Ask CodeObsess to work on a ticket in your ticket tool.

Before you start, finish the [first setup](https://docs.codeobsess.com/getting-started/first-setup.md) and make sure you can run tickets: your Claude account is connected, or your company has an AI key. See [Which AI runs a ticket](https://docs.codeobsess.com/ai/which-ai.md).

## Ask CodeObsess

> [tab] GitHub Issues
>
> Open an issue in one of your chosen repositories and write `@codeobsess` in the issue, or in a new comment on it. Type `@codeobsess` in full; GitHub doesn't suggest apps.
>
> CodeObsess reacts with 👀 and posts a status comment, usually within a few minutes.

> [tab] Linear
>
> Delegate the ticket to CodeObsess, or mention CodeObsess in it, and write what you need.
>
> During setup, Home can also create a small sample ticket in your first Linear team with **Create the ticket**. Open it and choose CodeObsess as its delegate.

> [tab] Jira
>
> Mention `@codeobsess` in a comment on an issue in a linked Jira project. You need to [connect your Jira account](https://docs.codeobsess.com/connect/jira.md#each-person-connects-jira) first.
>
> CodeObsess posts a status comment, usually within a few minutes.

## Follow the run

* The ticket shows the run's progress and, at the end, the report and the pull request.
* In CodeObsess, **Tickets** lists the ticket. Open it to see the conversation, the plan, the pull requests and the screenshots.
* If CodeObsess asks you something, the ticket says **Waiting for your reply.** See [Replying](https://docs.codeobsess.com/tickets/replying.md).

Next: [How a run works](https://docs.codeobsess.com/tickets/how-a-run-works.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.