Jira Service Management is getting a new navigation

We’re in the process of rolling out these changes and the documentation may not match your experience. Bear with us while we update it to reflect the new changes. More about navigating the new Jira

·

What are alert priorities?

The alert priority level conveys the severity of an alert, and affects who is notified, what notifications they receive, and how they receive those notifications.

By default, alert priorities scale from:

P5 - Informational
P4 - Low
P3 - Moderate
P2 - High
P1 - Critical

When the alert priority is updated, the notification flow for that alert will restart if the new priority is higher than the previous priority level.

Alerts can have the same, or a different level of priority as the incident so that you can control what alerts are sent for each of your priorities (in this case, incident priorities). Read more about priorities.

For example, for a P3 incident, you might only want to send P4 level alerts. By default, the top 5 alert priorities will be assigned to the top 5 incident priorities, and any new incident priority levels will be assigned to the lowest Apps > Opsgenie alert priority (P5 - informational). These can be managed in your global settings by a Jira admin, and will affect every service project using incident management.

Assign alert priorities to incident priorities

  1. From your service project, select Project settings, then Operations, then Incident management.

  2. Select Assign alert priorities.

Responder alerts

Alerts will automatically be created when someone is assigned, added as a responder or owns a service on the incident. We recommend adding the Responders field to each of your incident request types so you can create and acknowledge responder alerts on a work item. Read more about responder alerts.

 

Still need help?

The Atlassian Community is here for you.