Jira Notifications

Automatically create Jira Cloud tickets when incidents occur and execute transitions (Done/Closed) upon recovery.

Prerequisites: Obtaining an Atlassian API Token

1. Log in to Atlassian

   Go to Atlassian Account Management.

2. Create an API Token

   Click “Create API token”, enter a label (e.g., “Manako”), and create it.

3. Copy the Token

   Copy the displayed token.

4. Confirm your site URL

   Check your Jira Cloud site URL (e.g., https://your-site.atlassian.net).

5. Confirm your project key

   Check the project key (e.g., OPS, PROJ) from the Jira project settings.

Manako Configuration

1. Open the “Notification Channels” menu in the dashboard
2. Click “Add Channel” and select Jira as the Type
3. Enter the following:
   • Email: Atlassian account email address
   • API Token: The token you created
   • Site URL: https://your-site.atlassian.net
   • Project Key: The key of the project where tickets will be created
   • Issue Type Name: Ticket type (e.g., Bug, Task)
4. Click “Add Channel”

Note

The Site URL must be an HTTPS URL with a *.atlassian.net domain. On-premises Jira Server/Data Center is not supported.

Caution

Project keys must be uppercase alphanumeric only (e.g., OPS, PROJ). Lowercase characters are not allowed.

Behavior

Manako Event	Jira Action
Incident Created	Issue creation (ADF format description + manako, incident labels)
Incident Recovered	Automatically executes Done/Closed/Resolved/Complete transition
Web Change Detected	Issue creation (change diff included in description + webchange label)

Transitions

Upon recovery, Manako searches the ticket’s available transitions for Done, Closed, Resolved, or Complete and executes it. If no matching transition is found, a warning is logged and the ticket remains in its current status.

Tip

Make sure your Jira workflow includes transitions named “Done” or “Resolved”. With custom workflows, auto-closing will not work if these transition names do not exist.