Jira

What it does

• Lets your AI engineers search issues and projects, for example to avoid duplicates or link related work.
• Lets them file a finding as a Jira issue when you ask them to.

Issues are never filed automatically. There is no setting that opens a ticket for every finding at or above a severity.

Requirements

• A Jira Cloud site and a project where issues can be created.
• Permission to manage integrations in your organization.

Connect

In Settings, Integrations, choose Jira and either:

1. Connect with OAuth. Approve access in Atlassian. BreachLine asks for read:jira-work, write:jira-work, read:jira-user and offline_access.
2. Use an API token. When sign-in with Atlassian is not available, choose Jira (Basic Auth) and connect with your Atlassian site, account email and an API token.

Permissions and data handling

• Credentials stay out of chat and are never shown again after you connect.
• An issue contains what the engineer writes, usually the finding’s title, severity, description, evidence summary and remediation. Restrict the project’s visibility to the people who should see security findings.
• GET /api/v1/integrations/jira reads a separate legacy configuration. Its auto_ticket_severity field has no effect. See Integrations endpoints.

Troubleshooting

Symptom	Check
No tickets appear	Tickets are filed only when you ask an engineer to file one. Check that Jira shows as connected in Settings, Integrations.
Authentication errors	The token or OAuth grant has not been revoked, and the account can create issues in the project.

Known limitations

• There is no automatic ticketing by severity.
• An engineer can use only the projects the connected Atlassian account can see.