Jira tickets

Turn incidents into Jira tickets

Want a record of each outage and someone to own the follow-up? Pingstack opens a ticket in the Jira project you choose when an incident starts, comments on it as the incident changes, and comments again when the check recovers.

How it works

• One ticket per incident. Status changes are added as comments, so the ticket keeps the whole story. If a delivery is retried, Pingstack finds the ticket it already opened instead of creating a duplicate.
• Your project, your issue type. Pick the project and issue type for each channel. It works with Jira Software and Jira Service Management projects on Jira Cloud.
• You choose the priority. Pick a Jira priority for down, late and degraded checks, or leave it to Jira. By default, down is Highest, late is High and degraded is Medium.
• Closed when it’s fixed. On recovery, Pingstack adds a closing comment with how long the incident lasted, and can move the ticket to the status you choose, such as Done.
• Check it before you rely on it. Test connection confirms the account, project, issue type, recovery status and priorities, without creating a ticket.

Set it up

1. In Atlassian, create a classic API token (Create API token, not the scoped kind) for the account Pingstack should use. That account needs permission to create issues in the project.
2. In Pingstack, add a Jira tickets channel to a notification group: enter your Jira site, the account’s email and API token, then pick the project, issue type and, optionally, a status to move tickets to on recovery from your Jira.
3. Test the connection, then add the group to checks. Incidents open tickets and recoveries close them.

Paging someone is a separate integration. Use Jira Service Management alerts, PagerDuty, or phone calls alongside tickets.