Create a Jira 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.
Prerequisites
The Jira integration must be connected before you can create tickets.
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 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 | 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 | 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 | 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 | Select | Highest, High, Medium, Low, or Lowest. Pre-filled from the anomaly weight: 8 and above Highest, 6 to 7 High, 3 to 5 Medium, 0 to 2 Low, and Medium for an anomaly without a weight. | |
| Description | Text | Pre-filled with the anomaly's description, which is the failed checks' messages or what someone wrote over them. |
Note
There is no issue type or labels field. Every issue is created as a Task, and no labels are set.
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, 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, weight, 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 above for what each one holds.
Step 5: Click Create Ticket. A success message appears and the issue is listed in the Tickets section.