Jira

Connect Jira to collect ticketing evidence with automated compliance tests, switched on per workspace.

Step-by-step guide: Connect Jira.

Connect with OAuth

1. On Compliance › Connectors, open Jira, click Connect and choose OAuth.
2. Sign in to Jira and approve Safeguard on its consent screen. Use an account that can approve apps for your organization, usually an administrator. Safeguard asks for read:jira-work, offline_access.
3. You return to Safeguard, and the card shows Verified once the first check succeeds.

Connect with an API token

1. In Jira:

   1. Log in to https://id.atlassian.com/manage-profile/security/api-tokens with the Atlassian account Safeguard will use.
   2. Select Create API token with scopes (or Create API token for an unscoped token).
   3. Give the token a name that describes what it does (for example Safeguard) and select an expiration date (1 to 365 days).
   4. Select Jira as the app the token can access, then select the read scopes Safeguard needs.
   5. Select Create, then select Copy to clipboard and save the token.

   Where to find the other values:

   • Atlassian account email: The email address of the Atlassian account you were logged in to when you created the token.
   • Site URL: The address of your Jira Cloud site (the URL you open Jira at).

   Jira shows the secret only once, so copy it before you leave the page.

   Jira's public documentation does not cover every step.

   Source: support.atlassian.com, checked 2026-10-07.

2. On Compliance › Connectors, open Jira, click Connect, choose API token and fill in:

   Field	What to enter
   Atlassian account email	Required. The account the API token was created on. API tokens authenticate as email + token.
   API token	Required. Create at id.atlassian.com → Security → API tokens. The token inherits this account’s Jira permissions. Stored encrypted and never shown again.
   Site URL	Required.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Jira and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Ticketing connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks