Skip to main content

Export findings to Jira

Connect Jira to AISafe and export findings as Jira issues. Your engineering team can track and remediate vulnerabilities in their existing sprint workflow.

Prerequisites​

  • An AISafe account with manager or higher role
  • A Jira account with permission to create issues in the target project
  • A completed assessment with findings to export

Step 1: Connect Jira​

  1. Navigate to Integrations in the AISafe dashboard.
  2. Click Connect Jira and authorize AISafe in your Atlassian account.
  3. Choose the default Jira project where exported issues should land.
  4. After you connect, finding pages show the Create issue button.

Step 2: Open an assessment's findings​

  1. Navigate to the assessment whose findings you want to export.
  2. Open the findings list.
  3. Filter by severity or status to find the findings you want to export.

Step 3: Export a finding​

  1. Click on a finding to open its detail page.
  2. Click Create issue (available to managers and above).
  3. Select the target Jira project and issue type (defaults to your configured values).
  4. AISafe creates the Jira issue with:
    • Summary: the finding title
    • Description: vulnerability description, evidence, proof-of-concept, and suggested fix
    • Severity: mapped to a Jira priority or custom field
    • Link: a URL back to the finding in AISafe
  5. The finding now shows the Jira issue URL.

Batch export​

To export multiple findings at once:

  1. On the findings list, select the findings you want to export (checkboxes).
  2. Click Export to Jira.
  3. AISafe creates a Jira issue for each selected finding.

Tracking export status​

AISafe records each export attempt on the finding. The finding shows:

  • The Jira issue number and URL
  • The export status (creating, created, failed, abandoned)
  • The timestamp of the export

If an issue exists for a finding, AISafe shows the existing issue link and skips creating a duplicate. If a later scan finds the same root cause and AISafe recorded a non-empty root-cause fingerprint, exporting that newer finding to the same Jira target reuses the existing Jira issue instead of opening another one.

Next steps​