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

# Jira

> Connect Jira Cloud to Iru Compliance with OAuth to collect projects, issues, workflows, change tickets, and Jira Service Management request evidence for audits.

### About Jira

The **Jira** source pulls **project configuration**, **issue metadata**, **workflow definitions**, **user and assignee information**, and **Jira Service Management** request data from **Jira Cloud** into Iru Compliance, where it becomes evidence you can tie to actions and controls. Iru connects through **Atlassian’s three-legged OAuth 2.0 (3LO)** authorization code flow. The integration is **read-only**: Iru does not create or change issues, projects, or workspace settings.

This connector is for **Jira Cloud** only. **Jira Data Center** (self-hosted) uses a different authentication model and is **not** supported by this source.

### How It Works

After you provide your **Cloud ID**, the connector wizard sends you to Atlassian to sign in and consent. Iru receives a short-lived **access token** and a **rotating refresh token**, and renews tokens automatically on sync cycles.

| Scope                    | What it allows                                        |
| ------------------------ | ----------------------------------------------------- |
| `read:jira-work`         | Read issues, projects, workflows, and attachments     |
| `read:jira-user`         | Read user profiles and assignee information           |
| `read:jira-service-desk` | Read Jira Service Management requests and SLA metrics |

| Detail             | Value                                                                                               |
| ------------------ | --------------------------------------------------------------------------------------------------- |
| **Category**       | Project management                                                                                  |
| **Authentication** | OAuth 2.0 (Jira Cloud 3LO)                                                                          |
| **Vendor plan**    | **Paid** Jira Cloud plan (**Free** tier does not support the OAuth API access this connector needs) |

Documentation hub: [Atlassian Support - Jira](https://support.atlassian.com/jira/). OAuth: [Jira Cloud OAuth 2.0 (3LO)](https://developer.atlassian.com/cloud/jira/platform/oauth-2-3lo-apps/), [OAuth 2.0 scopes](https://developer.atlassian.com/cloud/jira/platform/scopes-for-oauth-2-3LO-and-forge-apps/). Cloud ID: [Retrieve your Atlassian Cloud ID](https://support.atlassian.com/jira/kb/retrieve-my-atlassian-sites-cloud-id/).

### Prerequisites

* A **paid** Jira Cloud site (**Free** does not support the OAuth API access required here).
* Your **Jira Cloud ID** (UUID). See **Find your Jira Cloud ID** below.
* Browser **pop-ups** allowed for your **Iru** domain so the OAuth step can open.
* The signing-in user does **not** have to be a Jira admin, but Iru can only read data that user can access. For broad evidence collection, use an account with at least:
  * **Browse projects** on every project you want Iru to read.
  * **Browse users and groups** (global permission) if you need user and assignee metadata.

A **dedicated service account** with read access across the right projects is often the easiest way to keep scope stable.

### Connect Jira to Iru

<Tabs>
  <Tab title="Jira">
    <Note>
      Complete this tab before you connect the source in Compliance.
    </Note>

    #### Find your Jira Cloud ID

    Your **Cloud ID** is the UUID Iru uses with `https://api.atlassian.com/ex/jira/{cloudId}`.

    <Steps>
      <Step title="Confirm Jira Cloud and paid access">
        This connector supports **Jira Cloud** with a **paid** plan that allows the OAuth API access Iru needs. Confirm you are not on a **Free** site that blocks the integration.
      </Step>

      <Step title="Open your Jira site">
        In a browser, open your Jira Cloud URL (for example `https://yoursite.atlassian.net`) so you know the **subdomain** you will substitute in the steps below.
      </Step>

      <Step title="Choose how you will look up the Cloud ID">
        Use **Option A** for a quick JSON lookup, or **Option B** if you already live in **Atlassian Admin**.
      </Step>

      <Step title="Option A: Tenant info (fastest)">
        In a new browser tab, open (replace `yoursite` with your Jira subdomain):

        `https://yoursite.atlassian.net/_edge/tenant_info`

        In the JSON response, copy the value of **`cloudId`**.
      </Step>

      <Step title="Option B: Atlassian Admin">
        Sign in at [admin.atlassian.com](https://admin.atlassian.com), select your organization, and find the Cloud ID in the browser URL (it appears after `/s/`).
      </Step>

      <Step title="Save the Cloud ID for Iru">
        Keep the UUID somewhere safe until you paste it into the Iru connector wizard’s **cloudId** field on the [**Iru Compliance**](#iru-compliance) tab.
      </Step>
    </Steps>

    <Note>
      Continue on the [**Iru Compliance**](#iru-compliance) tab.
    </Note>
  </Tab>

  <Tab title="Iru Compliance">
    <Note>
      Finish the [**Jira**](#jira) tab first so you have your **Cloud ID** for the connector wizard.
    </Note>

    <Steps>
      <Step title="Open Sources">
        In Iru Compliance, on the left navigation bar, expand **Compliance** and select **Sources**.

        <Frame>
          <img src="https://mintcdn.com/iru/7HsGH7lnQ8GpVmI0/assets/media/images/iru-navigation-compliance-sources.png?fit=max&auto=format&n=7HsGH7lnQ8GpVmI0&q=85&s=595982441fd777b333b3ecfea24adc24" alt="Left navigation: Compliance expanded, Sources selected" width="424" height="1056" data-path="assets/media/images/iru-navigation-compliance-sources.png" />
        </Frame>
      </Step>

      <Step title="Turn on Jira">
        Find **Jira** (set **Category** to **Project management** or use **Search by name or description**). On that card, turn on the **toggle**. A browser tab opens the connector wizard.
      </Step>

      <Step title="Step 1 of 2: Configure server variables">
        Enter your **Cloud ID** in the **cloudId** field, then select **Configure Server Variables**. Wait for confirmation that server variables updated successfully before continuing.
      </Step>

      <Step title="Step 2 of 2: OAuth">
        Select **Launch OAuth Authentication**. When the Atlassian popup opens, sign in and click **Accept** to grant the requested permissions.
      </Step>

      <Step title="Finish the connection">
        When the popup closes, Iru completes the OAuth exchange. When the connection succeeds, the wizard shows **Connection Configured**.
      </Step>

      <Step title="Confirm the source is Active">
        Close the **Iru is requesting access to external services** browser tab, then return to **Compliance** → **Sources** and confirm the **Jira** card is **Active**.
      </Step>
    </Steps>
  </Tab>
</Tabs>

### Troubleshooting

<AccordionGroup>
  <Accordion title="Nothing opens when you turn the source on">
    Check **pop-up blocker** settings for the Iru site and try **Launch OAuth Authentication** again.
  </Accordion>

  <Accordion title="Failed to update server variables">
    The wizard link may have expired. Turn **Jira** off and back on in **Sources**, then enter your **Cloud ID** again.
  </Accordion>

  <Accordion title="Missing projects or issues">
    The account that completed OAuth may lack **Browse projects** on some spaces. Adjust Jira permissions or connect with a **service account** that has the read coverage you need.
  </Accordion>

  <Accordion title="Token expired or reconnect prompts">
    Jira Cloud uses a **rotating refresh token** with a **90-day** validity window. If the connection is idle longer than that, complete the OAuth flow again from the **Jira** source card.
  </Accordion>

  <Accordion title="Jira Free plan">
    The **Free** tier does not support the OAuth API access this connector requires. Use a **paid** Jira Cloud plan to connect.
  </Accordion>

  <Accordion title="Wrong site or wrong Cloud ID">
    Confirm the **Cloud ID** matches the site you intend (see **Find your Jira Cloud ID**). A mismatch points Iru at the wrong tenant.
  </Accordion>
</AccordionGroup>

### Considerations

<CardGroup cols={2}>
  <Card title="Refresh tokens and idle connections" icon="circle-info">
    Iru refreshes access tokens on sync cycles. If sync does not run for **90 days**, plan to **re-authenticate** through the source card.
  </Card>

  <Card title="Heavy projects and retention" icon="shield">
    Large projects produce large histories. Narrow project scope where you can, and align **retention** and **privacy** policies before relying on workflow evidence in audits.
  </Card>
</CardGroup>

### Related Articles

<CardGroup cols={2}>
  <Card title="Sources Management" icon="plug" href="/en/compliance/sources-management">
    Browse and manage every Compliance source.
  </Card>

  <Card title="Getting Started With Compliance" icon="rocket" href="/en/compliance/getting-started-with-compliance">
    Frameworks, actions, and **Artifacts**.
  </Card>

  <Card title="Iru Overview" icon="layer-group" href="/en/iru/platform-overview/iru-overview">
    How Endpoint, Compliance, and Identity fit together.
  </Card>

  <Card title="Artifacts Management" icon="folder-open" href="/en/compliance/artifacts-management">
    Upload, review, and organize evidence from sources and actions.
  </Card>
</CardGroup>