Connect Jira

Before you begin

Complete the prerequisites in Connect Jira, including a restricted Jira identity, reachable HTTPS base URL, target project/issue type, and accepted required fields.

Open the feature

Open Settings → Integrations → Jira and keep a synthetic OpsKnight service and incident ready.

Configure the end-to-end workflow

1. Follow Connect Jira to save encrypted credentials and pass the connection test.
2. Map the synthetic service to the intended Jira project and issue type.
3. Follow Configure Jira webhooks and send a controlled webhook test.
4. Open the synthetic incident and create its Jira issue.
5. Change one supported field from OpsKnight and verify Jira, then change one supported field in Jira and verify the webhook-driven OpsKnight state.

What OpsKnight does

Rendering an incident performs no hidden Jira request. Explicit actions, webhooks, and background work update persisted link/sync state. Connection, project mapping, field validation, and webhook delivery therefore need separate verification.

Verify the integration

Require the expected Jira key, URL, project, issue type, status, assignee, and last sync direction/time. Confirm repeated webhook delivery does not create a duplicate link or transition.

Disconnect or undo

Stop webhook delivery, remove/disable mappings, and rotate/revoke credentials according to Jira troubleshooting. Existing Jira issues are not automatically deleted.

Troubleshooting

Capture the OpsKnight incident ID, Jira key, direction, operation time, correlation ID, and sanitized provider response. Then use the dedicated troubleshooting guide.

Next steps

• Jira connection reference
• Jira webhook configuration