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

# Setup

> Connect Jira to Prizm via OAuth, configure project and priority mappings, and set up the webhook for bidirectional sync.

<script type="application/ld+json">
  {`{
            "@context": "https://schema.org",
            "@type": "TechArticle",
            "headline": "Jira Setup",
            "description": "Connect Jira to Prizm via OAuth, configure project and priority mappings, and set up the webhook for bidirectional sync.",
            "url": "https://docs.dqlabs.ai/integrations/jira/setup",
            "publisher": {
              "@type": "Organization",
              "name": "DQLabs Inc",
              "logo": "https://media.brand.dev/332adc35-5bc4-4d2b-bf78-256aa4a5e414.svg"
            }
            }`}
</script>

## Connecting Jira to Prizm

Setting up the Jira integration involves three steps: authorizing Prizm to access your Jira Cloud account via OAuth, configuring which Jira project and issue type Prizm should use, and optionally enabling a webhook so that Jira status changes sync back to Prizm in real time.

### Prerequisites

* 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

***

## Step 1: Authorize with Atlassian

Navigate to **Organization** → **Integration** and click the **+** button to open the Channels catalog. Select the **Jira** tile.

Prizm redirects you to Atlassian to sign in and grant Prizm access to your Jira Cloud instance. After approving access, you are returned to Prizm. The **Site** (your Jira URL) and **Cloud ID** are populated automatically from the OAuth handshake.

<Note>
  If a Jira integration already exists, clicking the Jira tile navigates to the existing configuration. To switch the connected Atlassian account, click **Reconnect** on the configuration page, which restarts the OAuth flow.
</Note>

***

## Step 2: Configure projects and issue types

<Steps>
  <Step title="Add a project">
    In the **Projects Config** section, click **Add project**. Select the Jira **Project Name** from the dropdown — this list is populated from the projects visible to the authorized Atlassian account. Select the **Issue Type** that Prizm should use when creating tickets in that project (e.g., Bug, Task, Story, Epic).
  </Step>

  <Step title="Set a default project">
    Toggle **Default** on the project row you want Prizm to use automatically. Exactly one project must be set as the default. You can add multiple projects and switch the default at any time.
  </Step>

  <Step title="Add additional projects (optional)">
    Click **Add project** again to configure additional project/issue-type combinations. This is useful when different teams or domains route to different Jira projects.
  </Step>
</Steps>

***

## Step 3: Configure priority mapping

In the **Priority** section, confirm how Prizm severity levels map to Jira priority codes. Click a number to change the mapping for any severity level.

| Prizm Severity | Default Jira Priority Code |
| -------------- | -------------------------- |
| Critical       | 1                          |
| High           | 2                          |
| Medium         | 3                          |
| Low            | 4                          |

Adjust these values if your Jira projects use a custom priority scheme where codes have different meanings.

***

## Step 4: Enable webhook for bidirectional sync

Check **Enable webhook** to allow Jira to push status, comment, priority, and assignee changes back to Prizm in real time. Without a webhook, sync only flows from Prizm to Jira.

After clicking **Update Integration**, Prizm generates a **Webhook URL**. Copy this URL — you need it in the next section.

<Note>
  If an alert has multiple Jira issues linked to it, status sync via webhook is disabled for that alert to avoid conflicting updates. Only alerts with a single linked Jira issue receive automatic status sync.
</Note>

***

## Step 5: Save the configuration

Click **Update Integration** (or **Validate Integration** first to confirm the connection). Prizm confirms the connection is active and begins creating Jira issues automatically for new data quality issues.

<Frame>
  <img src="https://mintcdn.com/dqlabs/zvhyMoXaSfHLzAih/images/image-69.png?fit=max&auto=format&n=zvhyMoXaSfHLzAih&q=85&s=65600836b2cecb583880dbb8824c6300" alt="Image" width="2410" height="1140" data-path="images/image-69.png" />
</Frame>

## Configuration reference

| Field                  | Required | Description                                                                                                             |
| ---------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Site**               | Auto     | Your Jira Cloud URL (e.g., `https://yourcompany.atlassian.net`). Populated automatically after OAuth authorization.     |
| **Cloud ID**           | Auto     | Unique identifier for your Jira Cloud instance. Populated automatically after OAuth authorization.                      |
| **Project Name**       | Yes      | The Jira project where issues will be created. Populated from the projects visible to the authorized Atlassian account. |
| **Issue Type**         | Yes      | The issue type for new tickets (e.g., Bug, Task, Story, Epic). Configurable per project.                                |
| **Default**            | Yes      | Marks one project as the fallback when no specific project is selected. Exactly one project must be set as default.     |
| **Priority: Critical** | No       | Jira priority code for Critical severity (default: 1).                                                                  |
| **Priority: High**     | No       | Jira priority code for High severity (default: 2).                                                                      |
| **Priority: Medium**   | No       | Jira priority code for Medium severity (default: 3).                                                                    |
| **Priority: Low**      | No       | Jira priority code for Low severity (default: 4).                                                                       |
| **Enable webhook**     | No       | Activates bidirectional sync. Prizm generates a Webhook URL to configure in Jira.                                       |

<Note>
  The Atlassian account used for OAuth must have permission to create issues in the configured Jira projects. Prizm needs: **Browse Projects** and **Create Issue** permissions. If Prizm cannot list projects after authorization, verify the account's project-level permissions in Jira.
</Note>