Jira Installed
Create Jira tickets from SnagSpy issues.
Jira
Connect Jira to SnagSpy to turn a confirmed investigation into a tracked ticket without losing the incident context.
Install the integration
i
The Jira connection is configured at organisation level. Only organisation administrators can save or replace it.
Set up →
The details you need
Open Integrations from your workspace, then choose Jira in the Ticketing section.
01
Open the Integrations page.
02
In Ticketing, select Jira.
03
Add your Jira site, project key, and Atlassian account.
04
Paste a Jira API token with access to the project.
05
Save. SnagSpy validates the connection before marking it connected.
Verify the connection
SnagSpy verifies the connection when you save it. The token is never returned by the API or pre-filled afterwards.
Important
Saving again replaces the previous token. SnagSpy cannot display a token that has already been saved.
Connect your Jira project
The connection is available to every issue in your organisation. Use the Jira project key, not its displayed name.
provider: jira
base_url: https://acme.atlassian.net
project_key: OPS
account: [email protected]
api_token: $JIRA_API_TOKENCreate a ticket from an issue
A SnagSpy issue never opens a ticket automatically. A person chooses Create in Jira after validating the diagnosis.
INC-1247Payment checkout failuresCritical
DiagnosisElevated latency in payment-service
Impact confirmed across checkout flow.
!
SnagSpy creates a claim before contacting Jira so two teammates cannot open duplicate tickets.
Keep the team in sync
The created ticket contains the SnagSpy issue identifier. Share the Jira link through your on-call process and automations from there.
01Issue confirmedDiagnosis ready
→02Ticket createdOPS-241
→03Link preservedIn SnagSpy
Troubleshoot a connection
Check the site URL, account, and project key. A validation error identifies the field or access Jira rejected.
Token rejected
Create a new API token in Atlassian, then save the connection again.
Project not found
Use the Jira project key, not the project name.
Ticket already in progress
Search Jira for the issue identifier before clearing a stuck claim.