Create a Ticket
The Create Ticket action automatically creates a new ticket when the Flow is triggered. It is typically used to open a ticket when an anomaly is detected or when an anomaly changes to a specific status.
Permission Required
You need the Manager role to edit and publish Flows. See Flow Permissions for details.
Prerequisites
- A connected ticketing integration.
- A Flow with an Anomaly Detected or Anomaly Status Changed trigger. The Ticketing category stays disabled in the List of Actions panel with any other trigger type.
Field reference
The Create Ticket Settings panel shows the ticket fields of the connected integration. Pick the tab for your tracker.
Dynamic tokens
The summary and description fields accept the {{anomaly_id}}, {{anomaly_type}}, {{datastore_name}}, {{container_name}}, {{check_description}}, and {{anomaly_message}} tokens, replaced for each anomaly when the Flow runs.
| Field | Required | Type | Description |
|---|---|---|---|
| Short Description | Text | A brief summary of the incident. | |
| Status | Text | The initial status of the incident, typed as free text. Accepts a status name or its ServiceNow numeric code: New (1), In Progress (2), On Hold (3), Resolved (6), Closed (7), or Canceled (8). Already filled in with New. | |
| Priority | Option | The priority level of the incident. Defaults to Moderate: - Critical: critical business impact. - High: significant business impact. - Moderate: moderate business impact. - Low: low business impact. - Planning: planning or informational. |
|
| Urgency | Option | How quickly the incident needs to be resolved: High, Medium, or Low (the default). | |
| Impact | Option | The impact of the incident on business operations: High, Medium, or Low (the default). | |
| Description | Text | Your own context for the assignee. The anomaly's datastore, table, failed checks, and a link back to Qualytics are added automatically. | |
| Category | Text | The ServiceNow incident category (for example, Data Quality). | |
| Subcategory | Text | A more specific classification within the category (for example, Validation Error). | |
| Assignment Group | Text | The group to assign the incident to, identified by its ServiceNow sys_id. |
|
| Assigned To | Text | The user to assign the incident to, identified by their ServiceNow sys_id. |
| Field | Required | Type | Description |
|---|---|---|---|
| Project | Option | The Jira project the issue is created in. The list holds the projects allowed on the integration, with the integration's default project preselected. Only shown when the integration has projects configured. | |
| Summary | Text | A brief summary of the issue. | |
| Status | Text | The initial status for the issue, typed as free text, such as To Do, In Progress, In Review, or Done. Already filled in with To Do. Whatever you type is sent as is, and Jira decides on submit whether a transition to it exists. | |
| Priority | Option | The priority level of the issue: Highest, High, Medium, Low, or Lowest. | |
| Description | Text | Your own context for the assignee. The anomaly's datastore, table, failed checks, and a link back to Qualytics are added automatically. |
Steps
Step 1: Navigate to the Flows page by clicking Flows on the left side panel.
Step 2: On the Definitions tab, click the Flow. On its canvas, click the dashed Action placeholder after the trigger, or the + handle at the bottom edge of a node.
Step 3: In the List of Actions panel, pick the Ticketing category, then click Create Ticket. The Create Ticket Settings panel opens on the right-hand side.
Step 4: Fill in the fields.
Step 5: Click Save. The node shows a CHANGED badge and the You have unpublished changes banner appears on the canvas.
Step 6: Click Publish to make the action live.