# Create a Jira Ticket

Source: https://userguide.qualytics.io/anomalies/how-tos/ticket/jira/create-ticket/

Open a Jira issue straight from an anomaly. The issue is linked to the anomaly as it is created, and the anomaly's own context is appended to the description.

> **Info: Prerequisites**
>
> The Jira integration must be [connected](https://userguide.qualytics.io/settings/integrations/ticketing/jira/how-tos/connection/add-connection/) before you can create tickets.

> **Info: Permissions**
>
> Creating a ticket needs the **Manager** role and the **Author** team permission on the anomaly's datastore. An **Admin** can create one regardless of team membership. See the [Permissions](https://userguide.qualytics.io/settings/integrations/ticketing/jira/deep-dive/permissions/) page for details.

## Field reference

The **Create New Ticket** form arrives with most values already filled in from the anomaly.

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Project** | Yes | Select | The Jira project the issue is created in. The list holds the projects the integration allows, each shown as its name and key, and it starts on the integration's **Default Project**. |
| **Summary** | Yes | Text | The issue's one-line summary. Pre-filled from the anomaly, for example `[Qualytics #123] Record anomaly in orders: price must be positive`. |
| **Status** | No | Text | The status the issue starts in, pre-filled with `To Do`. Type the name your workflow uses. It is sent exactly as typed, and Jira decides on submit whether a transition to it exists. |
| **Priority** | No | Select | Highest, High, Medium, Low, or Lowest. Pre-filled from the anomaly's [impact](https://userguide.qualytics.io/anomalies/deep-dive/triage/impact/): Critical suggests Highest, High suggests High, Medium suggests Medium, and Low suggests Low. An anomaly without an impact suggests Medium. |
| **Description** | No | Rich text | Pre-filled with the [anomaly's description](https://userguide.qualytics.io/anomalies/deep-dive/anomaly-details/description/), which you can edit. The field is a Markdown editor that supports headings, bold and italic, inline code, quotes, lists, and tables, so what you see while writing is how the Jira issue shows it. Up to 32,000 characters. Leaving it empty does not open an issue with an empty description: the anomaly's description is used instead, and an anomaly without one gives the issue only the panel described below. |

> **Note**
>
> There is no issue type or labels field. The issue type is the one set for the selected project in the integration settings, `Task` unless another was picked, and no labels are set. See [Add Jira Connection](https://userguide.qualytics.io/settings/integrations/ticketing/jira/how-tos/connection/add-connection/#fields).
>
> An **Assignee** field is added only when the anomaly has an assignee whose email address Jira can match to an account. Jira Cloud hides email addresses by default, so most forms never show it.

## What Qualytics Adds to the Issue

Whatever you write in **Description** is kept (or the anomaly's description, when you cleared the field), and the anomaly's context is appended below it in an info panel headed **Qualytics Anomaly Linked**. The panel carries:

- The anomaly's ID, status, type, impact, number of anomalous records, and detection time.
- The datastore and table (or file), each linked back to its page in Qualytics, plus partition, segment, tags, and assignees when the anomaly has them.
- A **View in Qualytics** link to the anomaly itself.

The form shows the same details in a collapsible footer under the **Description** field, so you can check what will be added before creating the issue.

## Steps

**Step 1**: Open the anomaly and scroll to the **Tickets** section.

**Step 2**: Click **Link or create ticket** . It sits in the empty row while nothing is linked, and at the top right of the section once something is.

**Step 3**: In the **Link Ticket** modal, click **Create New Ticket**  at the bottom.

**Step 4**: Fill in the required fields. See the [Field reference](https://userguide.qualytics.io/anomalies/how-tos/ticket/jira/create-ticket/#fields) above for what each one holds.

**Step 5**: Click **Create Ticket**. A success message appears and the issue is listed in the **Tickets** section.

*Last updated: October 28, 2026.*
