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

# Tickets

> Learn what a ticket is in Ravenna, how a request moves from first message to closed, and how to work a ticket from the ticket page.

A ticket is one request for help, tracked from the moment someone asks until the work is done. Every ticket belongs to a [channel](https://docs.ravenna.ai/documentation/tickets/channels.md) in a workspace, has a requester, and has a number that starts with the channel's prefix, for example `HELP-123`. The whole conversation lives on the ticket and stays in sync with the Slack thread, Teams thread or email it started from, so your team and the requester never have to switch tools.

## How tickets work

**1. Someone asks for help**

A ticket starts from a Slack or Microsoft Teams message, an email, a [form](https://docs.ravenna.ai/documentation/tickets/forms/overview), the [Portal](https://docs.ravenna.ai/documentation/platform/portal.md), or the web app. Workflows, integrations and the API can create tickets too. Ravenna sets the [requester](https://docs.ravenna.ai/documentation/tickets/roles.md#requester) to the person who asked.

**2. An AI agent can answer first**

If the channel has an [AI agent](https://docs.ravenna.ai/documentation/automate/agents/overview), it replies first, using your knowledge and tools. While the agent handles the conversation, the ticket stays **unpublished**: it has no number, it's hidden from views, and notifications, SLAs and automations are paused. When the agent can't resolve the request, it escalates and publishes the ticket to your team.

**3. The ticket lands in a channel**

The [form](https://docs.ravenna.ai/documentation/tickets/forms/overview) answers, [type](https://docs.ravenna.ai/documentation/tickets/types), [priority](https://docs.ravenna.ai/documentation/tickets/organize/priorities.md), [category](https://docs.ravenna.ai/documentation/tickets/organize/categories.md) and [tags](https://docs.ravenna.ai/documentation/tickets/organize/tags.md) describe the request, and [workflows](https://docs.ravenna.ai/documentation/automate/workflows/overview) can set them automatically. Your team finds the ticket in [views](https://docs.ravenna.ai/documentation/tickets/organize/views.md).

**4. Your team works it**

The [assignee](https://docs.ravenna.ai/documentation/tickets/roles.md) owns the ticket and followers stay informed. Reply to the requester, or leave a [private note](https://docs.ravenna.ai/documentation/tickets/private-notes.md) for your team. Break the work down with [tasks](https://docs.ravenna.ai/documentation/tickets/tasks.md), [approvals](https://docs.ravenna.ai/documentation/tickets/approvals/overview) and [subtickets](https://docs.ravenna.ai/documentation/tickets/relations.md), while [SLAs](https://docs.ravenna.ai/documentation/measure/slas.md) track response and resolution times.

**5. It's resolved and closed**

The ticket's [status](https://docs.ravenna.ai/documentation/tickets/organize/statuses.md) moves from **Open** through **In Progress** and **Waiting** to **Done** and **Closed**. Archive tickets you no longer need in your lists.

## The ticket page

Open a ticket in the web app to read and work everything about it on one page.

| Area | What it holds |
| - | - |
| [Header](#header) | Back link, ticket navigation, **Assign to me**, Ravenna Assistant and the actions menu |
| [Banners](#banners) | Notices when a ticket is archived, merged, shared, unpublished or waiting on your approval |
| [Title and description](#title-and-description) | What the request is about, its source and its attachments |
| [Tabs](#tabs-and-sidebar) | **Subtickets**, **Tasks** and **Links** by default |
| [Sidebar](#tabs-and-sidebar) | Ticket fields, requester context, SLAs, dates and knowledge |
| [Conversation](#conversation) | Replies, private notes and the activity history |
| [Action dock](#action-dock) | The composer, status and assignee pickers, archive and ticket arrows |

### Header

| Control | What it does |
| - | - |
| **Tickets** | Returns to your ticket list |
| Previous and next arrows | Open the previous or next ticket in the view |
| **Assign to me** | Assigns the ticket to you |
| Ravenna Assistant | Opens [Ravenna Assistant](https://docs.ravenna.ai/documentation/automate/copilot/overview) |
| Actions menu (**...**) | Opens every ticket action. See [Actions menu](#actions-menu). |
| Sidebar toggle | Shows or hides the sidebar |

### Banners

| Banner | When it shows | Action |
| - | - | - |
| Archived | The ticket is archived | **Unarchive Ticket** |
| **Merged into** | The ticket was [merged](https://docs.ravenna.ai/documentation/tickets/merge-tickets.md) into another | **Unmerge Ticket** |
| **This ticket is shared to:** / **from:** | The ticket is [shared](https://docs.ravenna.ai/documentation/tickets/share-tickets.md) with another workspace | **Unshare Ticket** |
| **This ticket is unpublished.** | An agent is still handling the conversation. See [How tickets work](#how-tickets-work). | None |
| **You are being asked to approve this ticket** | You are an [approver](https://docs.ravenna.ai/documentation/tickets/approvals/overview) | Approve or decline |

[Incidents](https://docs.ravenna.ai/documentation/tickets/incidents.md) also show an incident header with their linked tickets.

### Title and description

Click the title or description to edit it. Chips above the description show:

* **Source**: where the ticket came from (Slack, Microsoft Teams, Email, Form, Ravenna, or an integration such as Jira or Linear). For Slack tickets, the chip opens the request thread.
* **Subticket of**: the parent ticket, when this ticket is a [subticket](https://docs.ravenna.ai/documentation/tickets/relations.md).
* **Ticket ID**: click to copy it.

Drop or paste files on the description to [attach them](https://docs.ravenna.ai/documentation/tickets/attachments.md#add-files-to-the-ticket-description). To format it, see [Format the description](#format-the-description).

### Tabs and sidebar

The tabs hold [**Subtickets**](https://docs.ravenna.ai/documentation/tickets/relations.md), [**Tasks**](https://docs.ravenna.ai/documentation/tickets/tasks.md) and [**Links**](https://docs.ravenna.ai/documentation/tickets/links.md) by default, each with a count. The sidebar holds the sections below. Sections with no data stay hidden.

| Section | What it shows |
| - | - |
| **Details** | [Status](https://docs.ravenna.ai/documentation/tickets/organize/statuses.md), [Priority](https://docs.ravenna.ai/documentation/tickets/organize/priorities.md), [Type](https://docs.ravenna.ai/documentation/tickets/types), [Channel](https://docs.ravenna.ai/documentation/tickets/channels.md), [Category](https://docs.ravenna.ai/documentation/tickets/organize/categories.md), [Assignee and Followers](https://docs.ravenna.ai/documentation/tickets/roles.md), [Tags](https://docs.ravenna.ai/documentation/tickets/organize/tags.md) |
| **Attributes** | Workspace [attributes](https://docs.ravenna.ai/documentation/tickets/forms/attributes.md) |
| **Form Fields** | Answers from the ticket's [form](https://docs.ravenna.ai/documentation/tickets/forms/overview) |
| **Approvers** | [Approval rounds](https://docs.ravenna.ai/documentation/tickets/approvals/rounds.md) and each approver's decision |
| **SLAs** | [SLA](https://docs.ravenna.ai/documentation/measure/slas.md) targets and their progress |
| **Requester**, **Assets**, **Endpoints** | [Cards](https://docs.ravenna.ai/documentation/tickets/cards.md) about the requester, their assets and their devices |
| **Requester's similar tickets** | Possible duplicates from the same requester, with **Copy URL** and **Archive** |
| **People** | The [requester and author](https://docs.ravenna.ai/documentation/tickets/roles.md) |
| **Dates** | **Due Date**, **Created**, **Updated**, **Resolved**, **Closed** and other timestamps. Use **Edit dates** to change them. See [Due dates](https://docs.ravenna.ai/documentation/tickets/due-dates.md). |
| **Knowledge** | Knowledge articles related to the ticket |

#### Arrange sections

Drag sections between the sidebar and the tab row to put them where you work. For example, move **Attributes** into a tab, or **Tasks** into the sidebar. Ravenna saves the layout to your account and uses it on every ticket you open.

### Conversation

The conversation lists public replies, [private notes](https://docs.ravenna.ai/documentation/tickets/private-notes.md) and ticket activity (status changes, assignments, SLA events and more) in order. Each message shows where it was sent from, for example **via Slack**. Email replies show their **Subject**, **To** and **Cc**.

### Action dock

The dock at the bottom of the ticket holds:

* **Composer**: press <kbd>R</kbd> for a public reply or <kbd>P</kbd> for a [private note](https://docs.ravenna.ai/documentation/tickets/private-notes.md). Attach files with the paperclip and send with <kbd>⌘</kbd> + <kbd>Enter</kbd>. On incidents, check **Send to all linked tickets** to post to every linked ticket.
* **Status** and **Assignee** pickers (<kbd>S</kbd> and <kbd>A</kbd>).
* **Archive**, and **Previous** and **Next** to move through the view.

> [!TIP]
>
> See every ticket shortcut in [Shortcuts](https://docs.ravenna.ai/documentation/get-started/shortcuts.md#ticket-shortcuts).

### Actions menu

Open **...** in the header. The same actions are in the command launcher (<kbd>⌘</kbd> + <kbd>K</kbd>).

| Action | What it does |
| - | - |
| **Snooze** | Hides the ticket until a date. See [Snooze](https://docs.ravenna.ai/documentation/tickets/snooze.md). |
| **Share** / **Unshare** | Shares the ticket with another workspace. See [Share tickets](https://docs.ravenna.ai/documentation/tickets/share-tickets.md). |
| **Move** | Moves the ticket to another channel. See [Move tickets](https://docs.ravenna.ai/documentation/tickets/move-tickets.md). |
| **Make Private** / **Make Public** | Changes who can see the ticket. See [Private tickets](https://docs.ravenna.ai/documentation/tickets/private-tickets.md). |
| **Summarize** | Asks Ravenna Assistant to summarize the issue and conversation. |
| **Similar Tickets** | Lists tickets similar to this one. |
| **Create KB Article** / **View KB Article** / **Regenerate KB Article** | Turns the ticket into a knowledge article. See [Generate articles](https://docs.ravenna.ai/documentation/automate/knowledge/generate-articles.md). |
| **Integrations** | Runs actions from connected integrations, such as creating a [Jira issue](https://docs.ravenna.ai/integrations/jira/ticket-replication.md). |
| **Add Parent**, **Add Sub Ticket**, **Remove Parent** | Manages [relations](https://docs.ravenna.ai/documentation/tickets/relations.md). |
| **Merge tickets** | Merges tickets. See [Merge tickets](https://docs.ravenna.ai/documentation/tickets/merge-tickets.md). |
| **Create incident**, **Link to incident**, **Unlink from incident** | Ties the ticket to an [incident](https://docs.ravenna.ai/documentation/tickets/incidents.md). |
| **Duplicate** | Opens a new ticket prefilled from this one. |
| Copy | **Copy URL**, **Copy Title**, **Copy Title as Link**, **Copy Git Branch Name**, **Copy as Markdown**, **Copy everything as Markdown** |
| **Archive** / **Delete** | Archives the ticket. **Delete** shows once a ticket is archived. |

## Format the description

### In the web app

Select text in the description to open the formatting menu (**Bold**, **Italic**, **Underline**, **Strikethrough**, **Code**, **Hyperlink**), or type Markdown. HTML typed into the description stays as plain text.

### Through the API

When you create or update a ticket through the API, Ravenna stores `description` exactly as you send it and applies formatting when the web app displays the ticket. GET responses and webhooks return the same raw string you sent.

> [!NOTE]
>
> Markdown is the most reliable format. Basic HTML also works.

| Renders | Shown differently |
| - | - |
| Bold, italic, strikethrough, inline code, `<u>` underline, `<mark>` highlight | Headings (`#` to `######`, `<h1>` to `<h6>`) show as paragraph text. Use bold text for section titles. |
| Code blocks: fenced (with an optional language for syntax highlighting), indented, or `<pre><code>` | Inline styles, colors and `<font>` lose their styling. The text is kept. |
| Bullet, numbered and nested lists; checklists (`- [ ]`, `- [x]`) | `<sub>`, `<sup>` and `<kbd>` show as plain text. |
| Blockquotes, including nested | `<details>` and `<summary>` show as plain text, with the collapsed content visible. |
| Links: Markdown, `<url>`, bare URLs, `<a href>`, `mailto:` | Table column alignment (`:--`, `--:`) is ignored. |
| Images (Markdown or `<img>`), tables, horizontal rules (`---`, `<hr>`) | `<script>`, `<style>` and `<iframe>` are removed. |
| A single newline becomes a line break. Backslash escapes like `\*` and `\#` work. | `<button>` and `<input>` are removed, but their label text stays. `javascript:` links show as plain text. |

A recommended description:

```markdown description.md theme={"system"}
**Laptop won't boot**
My laptop shows a black screen after the latest update.

- Model: MacBook Pro 14"
- Started: this morning

- [x] Restarted the laptop
- [ ] Tried safe mode
```

Send the file with `jq --rawfile`, so you don't have to escape JSON by hand. `queueId` is the ID of the channel the ticket goes to:

```bash theme={"system"}
curl --request POST \
  --url https://core.ravenna.ai/api/tickets \
  --header 'x-ravenna-api-token: <api-key>' \
  --header 'Content-Type: application/json' \
  --data "$(jq -n --rawfile d description.md --arg q '<channel-id>' \
    '{title: "Laptop won'\''t boot", priority: "LOW", queueId: $q, description: $d}')"
```

Learn more about how tickets fit with workspaces, agents and workflows in [Core concepts](https://docs.ravenna.ai/documentation/get-started/concepts.md)


## Related topics

- [Merge tickets](https://docs.ravenna.ai/documentation/tickets/merge-tickets.md)
- [Move tickets](https://docs.ravenna.ai/documentation/tickets/move-tickets.md)
- [Share tickets](https://docs.ravenna.ai/documentation/tickets/share-tickets.md)
- [Private tickets](https://docs.ravenna.ai/documentation/tickets/private-tickets.md)
- [Ticket replication](https://docs.ravenna.ai/integrations/jira/ticket-replication.md)


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