Export findings to Jira
Track a finding in Jira, in a source repository, or in several destinations. Each export creates one ticket in the destination you select.
Configure destinations
- Connect Jira under Integrations using an account with access to the target project.
- Open the assessment or application project's Settings.
- Add a Jira exporter and select its project and issue type.
You can add several destinations, including two GitHub repositories and Jira. Project destinations are available to that project's assessments. Export destinations can differ from the repositories scanned. If you change an exporter's credentials, they must still reach the same destination. To send tickets somewhere else, create another exporter.
If you rename a connected repository, its exporter keeps sending tickets to it. Before writing, AISafe checks the repository's identity and current name, so another repository that takes the old name does not receive those tickets.
Export a finding
- Open the finding and click Create issue. Export requires manager access or higher.
- Choose a destination. The picker shows existing tickets and connections that need repair.
- Review the full finding preview, then click Create issue.
AISafe builds the ticket from the saved finding, including its evidence and a link back to AISafe. If the result exceeds the destination's limit, the preview does not let you export the full finding. You can explicitly select Summary with evidence link, which keeps impact, remediation, and affected source paths while listing omitted evidence. The full evidence link requires AISafe access. AISafe never silently truncates a full finding or splits it into several tickets.
Export several findings
Select findings in the assessment table, select one export destination, and choose full findings or summaries. AISafe reports each result separately. If AISafe refuses to export one finding, it still exports the others.
Ticket history and retries
You can deliberately give the same finding a ticket in repository A and another in repository B. AISafe tracks the status of each ticket independently. If you export a finding again to the same destination, AISafe returns the ticket that already exists there. When a finding recurs across scans and has a recorded root-cause fingerprint, AISafe also reuses the ticket it created in that destination.
If a ticket was created but AISafe has no link to display for it, the ticket still counts as created. When you disable or remove an exporter, AISafe keeps its earlier ticket history.
When an export fails
If an export fails, AISafe tells you whether a ticket may already exist and what to do next. The Create issue control offers that next step. When you export several findings, each failed row shows its own next step.
| What happened | Was a ticket created? | What to do |
|---|---|---|
| AISafe could not connect to the tracker | No, nothing was sent | Try again in a moment |
| The tracker stopped responding before it confirmed the ticket | Maybe | Check the tracker for the ticket before you retry. Retrying without checking can create a duplicate |
| The tracker returned a server error | Maybe | Check the tracker before you retry |
| Linear did not confirm the new issue in time | No duplicate is possible | Retry. AISafe reuses the same issue ID, so Linear cannot create a second copy |
| The tracker is limiting requests | No | Try again in a few minutes |
| The tracker refused AISafe's access | No | An organization owner reconnects the tracker, then you try again |
| The tracker refused to create the ticket | No | Check that the destination in the exporter settings still exists and accepts new issues |
AISafe tries again on its own when a connection fails before anything is sent. It does not repeat a request that may have reached the tracker, so it never creates a duplicate ticket by itself.