Skip to main content

Jira

The AISafe Jira integration lets you export findings as Jira issues from the AISafe dashboard, integrating security findings into your team's existing sprint planning and issue tracking workflow.

How it works​

Connecting Jira to your AISafe organization gives AISafe the ability to create issues in your Jira projects. From any assessment's findings page, you can click Create issue to export a finding as a Jira issue. The issue includes the finding title, description, severity, evidence, and a link back to the finding in AISafe.

Connecting Jira​

  1. Navigate to Integrations in the AISafe dashboard.
  2. Click Connect Jira and authorize AISafe in your Atlassian account.
  3. Add an exporter in assessment or project Settings, selecting the Jira project and issue type.
  4. Add more destinations as needed, including several repositories from the same provider.

Exporting findings​

From a finding detail page or the findings list:

  1. Click Create issue (available to managers and above).
  2. Select a configured destination and review the full finding preview.
  3. If the full finding exceeds the destination limit, explicitly choose a summary with an authenticated evidence link.
  4. Click Create issue to create the ticket. Each destination keeps its own ticket history.

AISafe records each export attempt on the finding, tracking the issue number, URL, and status. If an issue exists for a finding, AISafe shows the existing issue link rather than creating a duplicate. For recurring findings with the same non-empty root-cause fingerprint, AISafe also reuses an existing Jira issue for the same export target across scans.

See Guide: Export findings to Jira for a step-by-step walkthrough.

If you enable outbound ticket synchronization, AISafe verifies that each ticket still belongs to the configured Jira project before closing or reopening it. Moving a ticket to another project stops those automatic changes; its historical link remains available. If the workflow offers no permitted close transition, AISafe reports the refusal beside that link. It only reports an issue as already closed when Jira confirms its current status.

Sync Jira status back to AISafe​

AISafe can also mark a finding's linked issue as closed or reopened when its status changes in Jira. Jira sends those updates through an Automation rule that you add:

  1. As the organization owner, create an issue-sync token for your Jira connection: POST /api/v1/integrations/connections/{connection_id}/jira-issue-sync-token. Send the request with an API key of yours that has the integrations:manage scope. The response contains the token, the webhook URL and the header name. The token is shown only once.

  2. In Jira, create an Automation rule that runs when an issue is transitioned, with a Send web request action:

    • URL: the webhook_url from the response.
    • Method: POST.
    • Header: the header_name from the response, with the token as its value.
    • Web request body: Issue data (Jira format).

    AISafe reads only the issue key and its status category: the done category means the issue is closed, and any other category means it is open.

  3. Close an exported issue in Jira, open the rule's audit log to check that the request succeeded, and check that the finding's issue link shows the issue as closed.

AISafe acts only on issues this connection exported and ignores the rest, so the rule can run for every issue in the project. Creating a new token replaces the old one, and disconnecting Jira turns the token off. If the rule's audit log shows 401 unknown_token, create a new token and update the rule's header. AISafe accepts up to 120 updates a minute for each token and answers 429 with a Retry-After header above that. AISafe never changes a finding's status because of a Jira update. Depending on the destination's sync settings, it notifies the finding's owner, who decides.