Skip to content

Commit edefc8a

Browse files
committed
docs: add Jira webhook setup for two-way incident sync
Made-with: Cursor
1 parent 3dcd8da commit edefc8a

1 file changed

Lines changed: 48 additions & 1 deletion

File tree

docs/cloud/integrations/alerts/jira.mdx

Lines changed: 48 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,9 +27,56 @@ After the ticket is created, a link to the Jira issue appears on the incident pa
2727

2828
<Note> If you connected the app before December 2025, you’ll need to re-authenticate the Jira app to change the **Reporter** or **Assignee** fields. You can do this by clicking the re-authentication link in the ticket form, or by going to your environment page and re-authenticating the app for the relevant environment.</Note>
2929

30-
<Tip> Elementary will not update the ticket in Jira when the incident is resolved or changed</Tip>
30+
<Tip>Without a Jira webhook, Elementary does not automatically update the linked Jira issue when you resolve or change an incident. Use the webhook setup below for two-way status sync.</Tip>
3131

3232
<img src="https://res.cloudinary.com/do5hrgokq/image/upload/v1768125455/incident-jira_idelv3.png" />
3333

3434
<img src="https://res.cloudinary.com/dvmtceykh/image/upload/v1739794590/jira_ticket_l6wknb.png" />
3535

36+
## Configure a Jira webhook for two-way sync
37+
38+
When a webhook is configured, Jira and Elementary stay aligned in real time: for example, closing the Jira issue can close the linked Elementary incident, and resolving the incident can update the Jira issue accordingly. Follow these steps in your Jira instance (Jira admin access required).
39+
40+
### Step 1: Open Jira webhook settings
41+
42+
1. Log in to Jira as an **Admin**.
43+
2. Click the **Settings** (gear) icon in the top right.
44+
3. Under Jira admin settings, select **System**.
45+
4. In the left sidebar, scroll to the bottom and click **WebHooks**.
46+
5. Click **Create a WebHook** (top right).
47+
48+
### Step 2: Fill in the webhook details
49+
50+
| Field | What to enter |
51+
| ----- | ------------- |
52+
| **Name** | A clear label (for example, `Elementary Sync`). |
53+
| **Status** | **Enabled**. |
54+
| **URL** | Paste the unique webhook URL shown in the Elementary product (environment / Jira integration UI). |
55+
| **Secret** | Generate the secret in Elementary, copy it, and paste it into the **Secret** field in Jira so payloads can be verified. |
56+
57+
### Step 3: Select events
58+
59+
1. In the **Events** section, open the **Issue** category.
60+
2. Enable **updated** only.
61+
3. Leave all other event checkboxes unchecked.
62+
63+
Issue updates are enough for Elementary to receive the changes needed to keep tickets and incidents in sync.
64+
65+
### Step 4: Scope to your project (recommended)
66+
67+
Limit traffic to the projects you care about using a JQL filter:
68+
69+
1. Find the **JQL filter** field on the webhook form.
70+
2. Enter:
71+
72+
```text
73+
project = "YOUR_PROJECT_KEY"
74+
```
75+
76+
Replace `YOUR_PROJECT_KEY` with your Jira project key (for example, `PROJ`).
77+
78+
### Step 5: Save and verify
79+
80+
1. Click **Create** at the bottom of the page.
81+
2. After Jira delivers its first event, the webhook status in the Elementary dashboard turns **green**, which indicates a successful connection.
82+

0 commit comments

Comments
 (0)