# Link an Existing Jira Ticket

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

Attach a Jira issue that already exists to an anomaly, instead of opening a new one.

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

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

## 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**: The **Link Ticket** modal opens with the most recently updated issues already listed. Type in the search bar to find others by key or by text, and use the **Project** selector beside it to narrow the list when the integration allows more than one project. When more issues match than the list shows, click **Load more tickets** at the bottom to fetch the next batch.

**Step 4**: Click the issue you want. A success message appears and the issue is listed in the **Tickets** section.

> **Note: The search only reaches the allowed projects**
>
> Qualytics searches the projects the integration allows, not everything the account can browse in Jira. An issue in a project that is not on that list cannot be found here. See [Add Jira Connection](https://userguide.qualytics.io/settings/integrations/ticketing/jira/how-tos/connection/add-connection/#fields).

Linking records the association only. The Jira issue is not modified, and no comment is posted on it until the anomaly's status or comments change.

> **Tip**
>
> Several issues can be linked to one anomaly, which is useful when more than one team tracks the same problem. Keep in mind that with **Anomaly status sync** on, every linked issue has a say in whether the anomaly moves. See [Anomaly status sync](https://userguide.qualytics.io/settings/integrations/ticketing/jira/deep-dive/sync-behavior/#anomaly-status-sync).

*Last updated: October 27, 2026.*
