Skip to main content

​
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. Documentation hub: Atlassian Support - Jira. OAuth: Jira Cloud OAuth 2.0 (3LO), OAuth 2.0 scopes. Cloud ID: Retrieve your Atlassian 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

Complete this tab before you connect the source in Compliance.

​
Find your Jira Cloud ID

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

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

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

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

Option A: Tenant info (fastest)

In a new browser tab, open (replace yoursite with your Jira subdomain):https://yoursite.atlassian.net/_edge/tenant_infoIn the JSON response, copy the value of cloudId.
5

Option B: Atlassian Admin

Sign in at admin.atlassian.com, select your organization, and find the Cloud ID in the browser URL (it appears after /s/).
6

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 tab.
Continue on the Iru Compliance tab.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try Launch OAuth Authentication again.
The wizard link may have expired. Turn Jira off and back on in Sources, then enter your Cloud ID again.
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.
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.
The Free tier does not support the OAuth API access this connector requires. Use a paid Jira Cloud plan to connect.
Confirm the Cloud ID matches the site you intend (see Find your Jira Cloud ID). A mismatch points Iru at the wrong tenant.

​
Considerations

Refresh tokens and idle connections

Iru refreshes access tokens on sync cycles. If sync does not run for 90 days, plan to re-authenticate through the source card.

Heavy projects and retention

Large projects produce large histories. Narrow project scope where you can, and align retention and privacy policies before relying on workflow evidence in audits.

Sources Management

Browse and manage every Compliance source.

Getting Started With Compliance

Frameworks, actions, and Artifacts.

Iru Overview

How Endpoint, Compliance, and Identity fit together.

Artifacts Management

Upload, review, and organize evidence from sources and actions.