> ## 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.

# Overview

> Connect Prizm to Jira to automatically create and track data quality issues as Jira tickets with full bidirectional sync.

<script type="application/ld+json">
  {`{
            "@context": "https://schema.org",
            "@type": "TechArticle",
            "headline": "Jira Overview",
            "description": "Connect Prizm to Jira to automatically create and track data quality issues as Jira tickets with full bidirectional sync.",
            "url": "https://docs.dqlabs.ai/integrations/jira/overview",
            "publisher": {
              "@type": "Organization",
              "name": "DQLabs Inc",
              "logo": "https://media.brand.dev/332adc35-5bc4-4d2b-bf78-256aa4a5e414.svg"
            }
            }`}
</script>

## What is the Jira integration?

The Jira integration connects Prizm data quality issues to Jira Cloud, allowing data teams to track remediation work alongside the rest of their engineering backlog. When a data quality issue is created in Prizm, a corresponding Jira ticket is created automatically in the configured project — complete with asset context, metric details, and a direct link back to Prizm. Changes to status, priority, comments, and assignee sync bidirectionally between both systems through a webhook.

For issues that require extended remediation or cross-team coordination, the Jira integration means data quality work enters the same sprint planning, triage, and resolution workflow as software engineering tasks — without requiring engineers to log into Prizm.

## What this integration enables

| Capability                      | Description                                                                                                                     |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **Automatic issue creation**    | Prizm issues are created as Jira tickets automatically once the integration is configured. No manual action required.           |
| **Rich issue context**          | Each Jira ticket includes asset name, attribute, measure, connection details, domain, product, and a direct link back to Prizm. |
| **Bidirectional status sync**   | Status changes in Jira sync back to Prizm via webhook. Resolving a ticket in Jira closes the linked Prizm issue.                |
| **Bidirectional priority sync** | Priority escalations or reductions in either system are reflected in the other.                                                 |
| **Bidirectional comment sync**  | Comments added in Jira appear in the Prizm issue thread, and vice versa.                                                        |
| **Assignee sync**               | Assignee changes in Jira update the owner on the linked Prizm issue.                                                            |
| **Multiple project support**    | Configure multiple Jira projects with different issue types. One project can be set as the default.                             |
| **Custom priority mapping**     | Map Prizm severity levels (Critical, High, Medium, Low) to your Jira priority scheme.                                           |

## Supported Jira versions

Prizm supports **Jira Cloud** via Atlassian OAuth. Jira Data Center is not currently supported.

## Workflow

1. A data quality issue is created in Prizm.
2. Prizm sends a request to Jira using the configured OAuth credentials.
3. Jira creates a corresponding issue in the configured default project with the issue name, description, priority, status, assignee, and comments.
4. A link to the Jira ticket appears on the Prizm issue detail page. Clicking it opens the ticket directly in Jira.
5. Any updates to status, priority, comments, or assignee in Prizm are pushed to the Jira issue via the REST API.
6. If the webhook is enabled, updates made in Jira (status changes, comments, priority, assignee) are sent back to Prizm in real time and reflected on the linked issue.
7. When the Jira issue is marked Done or Resolved, Prizm automatically closes the linked data quality issue.

## Prerequisites

Before connecting Jira to Prizm, you need:

* A Jira Cloud account
* Permission to authorize OAuth applications in your Atlassian organization
* At least one Jira project where data quality issues will be created
* Admin or privileged user access in Prizm to configure integrations

<CardGroup cols={2}>
  <Card title="Setup" icon="gear" href="/integrations/jira/setup">
    Connect Jira to Prizm — OAuth authorization, project configuration, and webhook setup.
  </Card>

  <Card title="Integration" icon="arrows-left-right" href="/integrations/jira/integration">
    How Prizm creates Jira issues, what data is included, and how sync works.
  </Card>
</CardGroup>