Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
Changes to Free and Standard plans in Jira Service Management
As of October 16, 2024, advanced incident management capabilities (such as major incidents and post-incident reviews) for Jira Service Management will move from Standard to Premium plans. After this point, only Premium and Enterprise plans will have access to these capabilities.
Existing projects in Free and Standard plans will continue to support existing request types and issue types. Read more about the plan changes.
A user should “escalate” an incident if the incident could be a major incident - such as a serious disruption to services (depending on your organization’s definition).
There are two main ways to escalate an incident - either mark the incident as major in Jira Service Management, or link it to an ongoing Opsgenie incident. For the latter, you must be connected to an Opsgenie site.
To mark the incident as major, you can simply turn on the Major incident toggle from your issue view. This will highlight the incident as major and move it to a different queue. Learn how to mark an incident as major.
Marking an incident as major doesn’t create an incident in Opsgenie.
To link a major incident to an Opsgenie incident:
From your service project sidebar, select Incidents.
Select Opsgenie incidents from the navigation on the left and switch to Opsgenie.
From Opsgenie, create a new incident or go to an ongoing incident that you want to link to this incident.
From the detail of the Opsgenie incident, select Link request from Jira Service Management requests.
Search for the incident in Jira Service Management and select Link.
Responders of the Opsgenie incident will be aware of the incident in Jira Service Management.
Note: When the Opsgenie incident is resolved, the original incident it was escalated from will also need to be resolved manually - the original incident will not automatically update.
Was this helpful?