Jira Integration

Overview

The Jira integration lets you push risks, audit findings, and incidents from Standardise directly into Jira Cloud as issues. This keeps your engineering and security teams aligned without manual copy-pasting between tools.

The integration uses OAuth 2.0 for secure authentication — no API tokens or service account passwords are stored. Standardise requests only the scopes needed to create and read issues in your selected Jira project.

Plan requirement: The Jira integration is available on the Pro plan and above.

Setup Steps

1. Navigate to Settings > Integrations and click Add Integration.
2. Select Jira as the provider. You will be redirected to Atlassian to authorise Standardise.
3. Sign in to your Atlassian account and grant Standardise access to your Jira Cloud site. The OAuth consent screen lists the permissions requested (read/write issues, read projects).
4. After authorisation, you will be redirected back to Standardise. Select the Jira project where issues should be created.
5. Configure field mappings and save the integration. You can test by creating a sample issue from a risk or incident.

Field Mapping

When an issue is pushed to Jira, Standardise maps ISMS data to Jira fields:

• Summary— the risk title, finding title, or incident title from Standardise.
• Description— the full description including relevant context such as severity, likelihood, and any linked controls.
• Priority— mapped from the ISMS severity or risk rating (e.g. critical maps to Highest, low maps to Low).
• Issue type— defaults to Task but can be configured to Bug, Story, or a custom issue type available in your project.
• Labels— automatically tagged with the source module (e.g. standardise:risk, standardise:incident) for easy filtering in Jira.

Creating Issues

Once connected, you can push items to Jira from three places in Standardise:

• Risk Register— open a risk and use the actions menu to create a Jira issue for tracking the risk treatment.
• Audit Findings— push individual findings from an internal audit to Jira for remediation tracking.
• Incidents— create a Jira issue from an incident to coordinate the response with your engineering team.

Each pushed item includes a backlink to Standardise, and the Standardise record stores the Jira issue key for cross-referencing.

Troubleshooting

• OAuth authorisation failed — Ensure you have admin or project-admin permissions in Jira Cloud. Jira Server (on-premise) is not supported.
• Project not appearing in list — Standardise only lists projects where the authorised user has permission to create issues. Check your Jira project permissions.
• Token expired — OAuth tokens refresh automatically. If the integration shows a connection error, try disconnecting and reconnecting via Settings > Integrations.