Connecting Jira
- Go to Integrations → Jira card and click Connect.
- Enter:
- Jira URL — your Atlassian instance URL (e.g.
https://myorg.atlassian.net) - Email — the Atlassian account email to authenticate as
- API token — generate one at id.atlassian.com/manage-profile/security/api-tokens
- Project key — the Jira project where issues will be created (e.g.
OPS)
- Jira URL — your Atlassian instance URL (e.g.
- Click Save.
Creating a Jira ticket from an incident
- Open the incident detail.
- Click Create Jira ticket in the Actions panel.
- Obsy creates an issue in your configured project with:
- Summary: the incident title
- Description: incident severity, affected services, and the Obsy incident URL
- Priority: mapped from incident severity (SEV1 → Highest, SEV4 → Low)
- The Jira ticket URL is linked in the incident header.
Status sync (webhook)
When the Jira ticket status changes (e.g. moved to “Done”), Jira can notify Obsy via webhook to update the incident timeline. Setup:- In Jira, go to Project Settings → Automation (or your Jira admin panel).
- Create an automation rule triggered by Issue transitioned.
- Add a Send web request action pointing to:
Replace
{orgId}with your Obsy organization ID (found in Settings → Organization). - Set the request body to the full issue JSON (Jira provides this by default).
Troubleshooting
'Authentication failed' when connecting
'Authentication failed' when connecting
Verify the email matches the Atlassian account that owns the API token. API tokens are account-specific — generating one as user A and entering user B’s email will fail.
Ticket created but no link appears in the incident
Ticket created but no link appears in the incident
Refresh the incident page. If the link still doesn’t appear, check Integrations → Jira for an error message.