> ## Documentation Index
> Fetch the complete documentation index at: https://docs.obsy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Jira

> Create Jira tickets from incidents and sync status back to Obsy.

The Jira integration lets you create a Jira issue directly from an Obsy incident and keep the two in sync — when the Jira ticket is updated, the incident timeline is updated automatically.

***

## Connecting Jira

1. Go to **Integrations → Jira card** and click **Connect**.
2. 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](https://id.atlassian.com/manage-profile/security/api-tokens)
   * **Project key** — the Jira project where issues will be created (e.g. `OPS`)
3. Click **Save**.

***

## Creating a Jira ticket from an incident

1. Open the incident detail.
2. Click **Create Jira ticket** in the Actions panel.
3. 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)
4. 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:**

1. In Jira, go to **Project Settings → Automation** (or your Jira admin panel).
2. Create an automation rule triggered by **Issue transitioned**.
3. Add a **Send web request** action pointing to:
   ```
   https://api.obsy.ai/api/v1/integrations/jira/webhook/{orgId}
   ```
   Replace `{orgId}` with your Obsy organization ID (found in **Settings → Organization**).
4. Set the request body to the full issue JSON (Jira provides this by default).

Obsy logs each webhook event in the incident timeline as "Jira ticket status changed to Done".

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="'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.
  </Accordion>

  <Accordion title="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.
  </Accordion>
</AccordionGroup>