How to Get Notified by Jira Service Management

What is Jira Service Management Notification?

Jira Service Management is Atlassian's service and incident management platform. Its Operations part handles alerts, on-call schedules and escalations, and it replaces Opsgenie. Xitoring creates an alert there when a server or check goes down and closes the same alert when it recovers.

Why Use Jira Service Management Notifications?

• Alerts that close themselves: the recovery closes exactly the alert the outage opened
• Priorities that match the problem: P1 for an outage, P3 for warnings such as high CPU or an expiring SSL certificate
• Your on-call setup decides who is paged: routing, schedules and escalations stay in Jira Service Management
• One alert per incident: repeated notifications update the open alert instead of creating new ones

Opsgenie Shuts Down on 5 April 2027

Atlassian stopped selling Opsgenie in June 2025 and switches it off on 5 April 2027; unmigrated data is deleted then. If your notification roles send to Opsgenie today, add Jira Service Management to them as described below, test it, then turn Opsgenie off in the role.

How to Configure Jira Service Management Notifications

Step 1: Create an API Integration

1. In Jira Service Management, open the operations page of the team that should receive alerts (on a new site, first go to Operations → Home, create a team and select Enable operations)
2. In the left navigation, select Integrations, then Add integration
3. Search for API and select it
4. Name it (e.g. "Xitoring"), optionally choose an Assignee team, and select Continue
5. Select Turn on integration
6. Copy the integration's API key

Step 2: Add It to a Notification Role

1. Log in to your Xitoring Dashboard
2. Open Notification Roles and select a role, or create a new one
3. Under Incident management, turn on Jira Service Management
4. Paste the API key

Step 3: Test and Save

1. Click Send test and confirm; a test alert appears in Jira Service Management
2. Click Create a new role, or Save changes for an existing role

For details and troubleshooting, see the Jira Service Management documentation.

Best Practices

• Create one API integration per team, so alerts land with the team that owns the service
• Use separate notification roles for critical and non-critical checks
• Keep Opsgenie and Jira Service Management both enabled in a role only while you test the move

Learn More

Explore all available Notification Channels to set up your ideal alerting workflow.