Jira

How this helps triage: when Jira is connected, Exhale looks up to three open issues that match the Pulse service or title and can cite them in the summary. If the token cannot read issues, that block is skipped.

After an incident, Growth or higher workspaces also use Jira on the Postmortem tab to link issues, attach a scrubbed summary as a comment, and create follow-ups from checklist items.

This is not incoming ingest and is distinct from JSM Operations (Opsgenie) Sources.

Connect

1. Sign in as a workspace admin.
2. Open Connections → Context → Ticketing → Jira.
3. Authorize Jira OAuth (read:jira-work, write:jira-work, and offline_access by default).
4. Test connection.
5. Disconnect clears the stored token.

Jira access tokens last about an hour; Exhale refreshes them with the stored refresh token when they are near expiry, and asks you to reconnect if that refresh fails.

Trial and Starter workspaces cannot connect (403).

After an incident

On Pulse Detail Reports → Postmortem, members and admins can Link, Attach, and create follow-ups when the connector status is configured. Outbound bodies are scrubbed titles and Markdown only — never raw webhook payloads.

Plan

Growth or higher.

API

Canonical paths are under /v1. Writes use the signed-in session and CSRF. Secrets are never returned on GET. Disconnect is DELETE /v1/auth/context-connectors/jira. Start is GET /v1/auth/context-connectors/jira/oauth/start.

Related

• Linear
• Context index