Jira Service Management

Page on-call through Jira Service Management

Already run on-call in Jira Service Management? Pingstack sends each incident there as an alert, and your schedules, routing rules and escalation policies decide who gets paged.

How it works

• One alert per incident. When a check goes down, late or degraded, Pingstack opens an alert. If the check’s status changes while it’s open, Pingstack adds a note to the alert. When the check recovers, the alert closes.
• You choose the priority. Pick P1 to P5 for down, late and degraded checks on each channel. By default, down is P1, late is P2 and degraded is P3.
• Moving from Opsgenie? Opsgenie shuts down in April 2027 and its teams are moving to Jira Service Management. This integration works with those teams once they’ve moved.
• Test before you rely on it. Send a test alert from the channel page. Pingstack waits for Jira Service Management to confirm it, then closes it, and tells you if anything went wrong.

Set it up

1. In Jira Service Management, open your team’s operations page, go to Integrations, add an API integration, turn it on and copy its API key.
2. In Pingstack, add a Jira Service Management channel to a notification group, paste the key and choose priorities.
3. Add the group to checks. Incidents and recoveries go to Jira Service Management.

Want a ticket for follow-up as well? Add Jira tickets to the same notification group.