Jira

Observer opens a Jira issue when an incident is published and transitions it when the incident resolves. One Observer incident maps to one Jira issue.

Set up#

1. •

   Create an API token#

   At id.atlassian.com, open Security, then API tokens, and create a token for the account that should own the issues. Note the account email and the token.

2. •

   Add the integration in Observer#

   In the console, open Alerts, choose Add alert, pick Jira, and enter:

   • Site: your Atlassian Cloud host, for example your-org.atlassian.net.
   • Account email and API token: the credentials from the previous step.
   • Project key: the project issues are created in, for example OPS.
   • Issue type: defaults to Task.
   • Resolve transition: the workflow transition used when the incident resolves. Defaults to Done.

   Choose org-wide or a single page, then save.

3. •

   Test it#

   Use Test on the row. A test issue should appear in the project. Delete or close it when you are done.

Required permissions#

A Jira API token uses Basic authentication and inherits the permissions of the account that created it. There are no OAuth scopes to grant. In the target project, that account needs:

If the account cannot perform one of these, the matching step is reported as a failure with the Jira error in the delivery result.

Lifecycle mapping#

Correlation is by label. Each issue carries a label derived from the Observer incident id (observer-incident-<id>). Updates comment on that issue and the resolve transitions it, so the lifecycle produces one issue, not several.

Troubleshooting#

• No issue is created: confirm the project key exists and the account can create issues of the configured type in that project. Jira returns a 4xx with the reason, which Observer surfaces in the delivery result.
• Authentication failures: the token must belong to the account email you entered. Re-create the token if unsure.
• Resolve does nothing: check the resolve transition name against the issue's workflow.