> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration

> How Prizm automatically creates Jira issues, what data is included, and how bidirectional sync works between Prizm and Jira.

<script type="application/ld+json">
  {`{
            "@context": "https://schema.org",
            "@type": "TechArticle",
            "headline": "Jira Integration",
            "description": "How Prizm automatically creates Jira issues, what data is included, and how bidirectional sync works between Prizm and Jira.",
            "url": "https://docs.dqlabs.ai/integrations/jira/integration",
            "publisher": {
              "@type": "Organization",
              "name": "DQLabs Inc",
              "logo": "https://media.brand.dev/332adc35-5bc4-4d2b-bf78-256aa4a5e414.svg"
            }
            }`}
</script>

## How the Jira integration works

Once the Jira integration is configured and active, Prizm automatically creates a Jira issue every time a data quality issue is raised in Prizm. No manual action is required. The Jira ticket is created in the configured default project using the selected issue type, and a direct link to the Jira ticket appears on the Prizm issue detail page.

If the webhook is enabled, changes made in either system — status, comments, priority, assignee — are synced back to the other in near-real time.

***

## Automatic issue creation

When a new issue is created in Prizm, Prizm sends a request to the Jira REST API and creates a corresponding issue in the configured default project. The Jira issue is populated with:

* **Summary**: the Prizm issue title
* **Priority**: mapped from the Prizm severity level (Critical → 1, High → 2, Medium → 3, Low → 4 by default)
* **Status**: Open
* **Assignee**: the owner set on the Prizm issue
* **Reporter**: the Prizm user who created the issue
* **Description**: see the template below

### Issue description template

Every Jira issue created by Prizm includes the following fields in the description:

| Field               | Description                                            |
| ------------------- | ------------------------------------------------------ |
| **Asset**           | Name of the data asset with the quality issue          |
| **Attribute**       | Specific column or attribute affected                  |
| **Measure**         | The quality measure or metric that triggered the issue |
| **Connection Type** | Type of data source (e.g., Snowflake, BigQuery)        |
| **Connection Name** | Name of the connection in Prizm                        |
| **Created By**      | Prizm user who created the issue                       |
| **Issue Key**       | Prizm issue identifier                                 |
| **Asset ID**        | Internal Prizm ID for the asset                        |
| **Attribute ID**    | Internal Prizm ID for the attribute                    |
| **Measure ID**      | Internal Prizm ID for the measure                      |
| **Application**     | Application context from the Prizm asset               |
| **Domain**          | Data domain classification                             |
| **Product**         | Associated data product                                |
| **Issue ID**        | Prizm issue ID                                         |
| **Creator User ID** | Prizm user ID of the creator                           |

The description also includes a direct URL back to the Prizm issue page, allowing engineers working in Jira to navigate to the full context with one click.

***

## Viewing the Jira link in Prizm

After a Jira issue is created, the Jira ticket number and a direct link to the issue appear on the Prizm issue detail page. Clicking the link opens the Jira ticket directly in a new tab.

***

## Bidirectional sync

When **Enable webhook** is turned on in the integration configuration, Jira and Prizm stay synchronized in real time. The following fields sync in both directions:

| Field           | Prizm → Jira | Jira → Prizm |
| --------------- | ------------ | ------------ |
| **Description** | ✓            | ✓            |
| **Comment**     | ✓            | ✓            |
| **Priority**    | ✓            | ✓            |
| **Status**      | ✓            | ✓            |
| **Assignee**    | ✓            | ✓            |

### Status sync behavior

When a Jira issue is marked as **Done** or **Resolved**, Prizm automatically closes the linked data quality issue. Status changes originating in Prizm (e.g., acknowledging or resolving an issue) are reflected in Jira via the REST API.

### Comment sync

Comments added in Jira are forwarded to the Prizm issue conversation thread via the webhook. Comments added in Prizm are posted to the Jira ticket via the Atlassian REST API. This keeps the full conversation visible to anyone working in either system.

### Priority sync

If a Jira issue's priority is escalated or reduced, the change is reflected on the linked Prizm issue. Likewise, if priority is updated in Prizm, the Jira ticket priority is updated to the corresponding mapped code.

<Note>
  If a Prizm alert has more than one Jira issue linked to it, status sync via webhook is disabled for that alert to prevent conflicting updates from multiple tickets. Only alerts with a single linked Jira issue receive automatic bidirectional status sync.
</Note>

***

## Without webhook (one-way sync)

If the webhook is not enabled, changes in Jira are not automatically reflected in Prizm. Updates made in Prizm (status, comments, priority) continue to be pushed to Jira, but changes made in Jira require a manual refresh or re-sync in Prizm.

For most use cases, enabling the webhook is strongly recommended for complete bidirectional sync.

***

## Permissions required

The Atlassian account connected via OAuth must have the following Jira permissions to create and update issues:

* **Browse Projects** — to list available projects
* **Create Issues** — to create new tickets
* **Edit Issues** — to update status, priority, and assignee
* **Add Comments** — to post comments from Prizm

<Tip>
  If your team uses Jira for sprint planning, the bidirectional status sync means data quality issues automatically close in Prizm when engineers mark the fix as Done in Jira — no manual cleanup required.
</Tip>