> For the complete documentation index, see [llms.txt](https://rosvelt.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rosvelt.gitbook.io/docs/core/organizations/projects/tickets.md).

# Tickets

## **What is a ticket?**

A ticket describes work to be done. When you create a ticket, AI agents can autonomously pick it up, plan the implementation, write code, run tests, and deliver the result — all without manual intervention.

### **Create a ticket**

1. Click the **New ticket** button in the sidebar (or use the keyboard shortcut).
2. Fill in the details (title, description, priority, labels, etc.).
3. Click **Create** — or **Create & add more** to batch-create tickets.

### **Ticket properties**

| Property          | Description                                 |
| ----------------- | ------------------------------------------- |
| **ID**            | Unique identifier                           |
| **Title**         | Short description of the work               |
| **Description**   | Rich text with full details                 |
| **Status**        | Current workflow state                      |
| **Priority**      | Urgency level                               |
| **Labels**        | Tags for categorization                     |
| **Confidence**    | AI's confidence score in the implementation |
| **Complexity**    | Estimated complexity of the work            |
| **Due date**      | Target completion date                      |
| **Relationships** | Parent/child and blocking dependencies      |

### **Statuses & workflow**

Tickets follow a defined lifecycle with **7 states**:

```
┌──────────┐     ┌──────────┐     ┌──────────┐     ┌──────────┐
│ Planned  │───▸│  Ready   │───▸ │ Working  │───▸│In Review │
└──────────┘     └──────────┘     └──────────┘     └──────────┘
                      │                │                │
                      ▼                ▼                ▼
                 ┌──────────┐     ┌──────────┐     ┌──────────┐
                 │ Stopped  │     │ Blocked  │     │Completed │
                 └──────────┘     └──────────┘     └──────────┘
```

#### **Transition rules:**

* If the ticket is assigned to Rosvelt, only Rosvelt can move tickets to `Working`, `In Review`, `Blocked`, or `Completed`.
* **Users** can move tickets between `Planned`, `Ready`, and `Stopped`.
* When creating a ticket, you choose between:
  * **Planned** — the ticket stays in the backlog until you move it to Ready.
  * **Ready** — the AI can immediately pick it up and start working.

### **Priorities**

AI agents consider priority when deciding which tickets to work on first. **Urgent** and **High** priority tickets are picked up before **Medium** and **Low**.

### **Labels**

Labels help categorize and filter tickets. Rosvelt provides **5 predefined labels**, and a ticket can have multiple labels. Labels are used in filters to quickly find relevant tickets.

### **Ticket relationships**

Tickets can be connected to each other with two types of relationships:

**CHILD\_OF (Sub-tickets)** — break large tickets into smaller sub-tasks.

*Example:*

* "Build user authentication" (parent)
  * "Create login form" (child)
  * "Implement JWT tokens" (child)
  * "Add password reset" (child)

**BLOCKED\_BY (Dependencies)** — mark when a ticket cannot proceed until another is completed.

*Example:* "Deploy to production" is `BLOCKED_BY` "Set up CI/CD pipeline".

When a ticket is blocked, AI agents **will not attempt to work on it** until the blocking ticket is completed.

### **Ticket threads**

Each ticket has threaded conversations for collaboration, real-time chat with AI agents.

Messages in threads can come from:

* `USER` — human team members
* `AGENT` — AI agents working on the ticket
* `SYSTEM` — automated system notifications


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://rosvelt.gitbook.io/docs/core/organizations/projects/tickets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.