# Create a ServiceNow Ticket

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

Create a new ServiceNow Incident directly from an anomaly in Qualytics. The new ticket is automatically linked to the anomaly and includes its context.

> **Info: Prerequisites**
>
> The ServiceNow integration must be [connected](https://userguide.qualytics.io/settings/integrations/ticketing/servicenow/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/servicenow/deep-dive/permissions/) page for details.

## Field reference

The **Create New Ticket** form asks for the following. Only the short description is required, and everything else can be left empty.

| Field | Required | ServiceNow field | Description |
| --- | --- | --- | --- |
| **Short Description** | Yes | `short_description` | A brief summary of the data quality issue. Pre-filled from the anomaly. |
| **Status** | No | `state` | The state the incident starts in. One of **New**, **In Progress**, **On Hold**, **Resolved**, **Closed**, or **Canceled**, and a numeric code can be typed instead. Defaults to **New**. |
| **Priority** | No | `priority` | **Critical**, **High**, **Moderate**, **Low**, or **Planning**. Pre-filled from the anomaly's [impact](https://userguide.qualytics.io/anomalies/deep-dive/triage/impact/): Critical suggests Critical, High suggests High, Medium suggests Moderate, and Low suggests Low. An anomaly without an impact suggests Moderate. |
| **Urgency** | No | `urgency` | **High**, **Medium**, or **Low**. Pre-filled from the anomaly's impact: Critical suggests High, High and Medium suggest Medium, and Low suggests Low. An anomaly without an impact suggests Medium. |
| **Impact** | No | `impact` | **High**, **Medium**, or **Low**. Filled from the anomaly's impact the same way as **Urgency**. |
| **Description** | No | `description` | The detail behind the issue, pre-filled from the anomaly as plain text, since a ServiceNow incident description does not show formatting. Up to 4,000 characters. The anomaly's own context is appended when you submit. Leaving it empty sends the anomaly's description instead; an anomaly without one gives the incident only the appended block. |
| **Category** | No | `category` | Has to match a category name in your instance exactly, including case. See [Find ServiceNow Values](https://userguide.qualytics.io/settings/integrations/ticketing/servicenow/how-tos/find-servicenow-values/#category-subcategory). |
| **Subcategory** | No | `subcategory` | Matched the same way as the category. |
| **Assignment Group** | No | `assignment_group` | The `sys_id` of the group, not its display name. See [Find ServiceNow Values](https://userguide.qualytics.io/settings/integrations/ticketing/servicenow/how-tos/find-servicenow-values/#assignment-group-sys_id). |
| **Assigned To** | No | `assigned_to` | The `sys_id` of the user, not a username or display name. A value ServiceNow cannot resolve leaves the incident unassigned. |

> **Note: The caller cannot be set**
>
> Every incident is opened by the integration's service account, and there is no field for the caller. See [What It Does Not Do](https://userguide.qualytics.io/settings/integrations/ticketing/servicenow/deep-dive/how-it-works/#what-it-does-not-do).

Choosing **Resolved**, **Closed**, or **Canceled** as the starting state fills in a close code and a close note automatically, because ServiceNow refuses those states without them.

## Steps

**Step 1:** Open the anomaly in Qualytics, scroll to the **Tickets** section, and click the **Link or create ticket** button.

**Step 2:** The **Link Ticket** modal opens with a search bar. This is the unified entry point for both linking existing tickets and creating new ones.

**Step 3:** Click the **Create New Ticket**  button next to the search bar.

**Step 4:** The **Create New Ticket** form opens. Fill in the fields described in the [Fields](https://userguide.qualytics.io/anomalies/how-tos/ticket/servicenow/create-ticket/#fields) section above.

**Step 5:** Click the **Create Ticket** button to submit.

**Step 6:** A success notification appears, and the new ticket is shown in the **Tickets** section of the anomaly.

The incident opens with what you wrote in **Description** as plain text (or the anomaly's description, when you cleared the field), and Qualytics appends a block below it holding:

- Anomaly ID, status, type, impact, number of anomalous records, and detection timestamp
- The datastore and table (or file), plus partition, segment, tags, and assignees when the anomaly has them
- A direct link back to the anomaly in Qualytics

> **Tip**
>
> If you need to link an existing ServiceNow incident instead of creating a new one, use the [Link Existing Ticket](https://userguide.qualytics.io/anomalies/how-tos/ticket/servicenow/link-existing-ticket/) flow.

> **Info: Need help finding Category or Assignment Group values?**
>
> Category, Subcategory, and Assignment Group values must match your ServiceNow instance exactly. See [Find ServiceNow Values](https://userguide.qualytics.io/settings/integrations/ticketing/servicenow/how-tos/find-servicenow-values/) for step-by-step instructions on looking them up.

*Last updated: October 28, 2026.*
