---
title: Update the priority of an SRM incident
description: If the priority of an incident should be changed, you can manually update it to reflect its new criticality.REVISE FOR SRM
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/service-reliability-management/sr-update-incident-severity.html
release: australia
product: Service Reliability Management
classification: service-reliability-management
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 1
breadcrumb: [Working with incidents in SRM, Working with SRM reliability tasks, Using Service Reliability Management, Service Reliability Management, ITOM AIOps, IT Operations Management]
---

# Update the priority of an SRM incident

If the priority of an incident should be changed, you can manually update it to reflect its new criticality.

## Before you begin

Role required: srm\_manager, srm\_responder, or srm\_admin

## Procedure

1.  Navigate to **Workspaces** > **Service Operations Workspace**.

    You're taken to your SRM Home page.

    **Note:** If you use other Service Operations Workspace \(SOW\) applications, you may see the SOW Home page instead of the SRM Home page. The SOW Home page includes SRM alerts and incidents in its metrics.

2.  From the primary navigation, select **Reliability tasks** \(\[Omitted image "icon-sr-reliability-tasks.png"\] Alt text: Reliability tasks icon\).

3.  Select the **Incidents** tab.

4.  In the Incident list view, select a **Priority** value from the list menu.

    -   1 - Critical
    -   2 - High
    -   3 - Moderate
    -   4 - Low
    -   5 - Planning \(default\)
5.  Select **OK**.

    The new priority is reflected in the incident list view and incident header and form field.


**Parent Topic:**[Working with incidents in SRM](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/service-reliability-management/sr-work-incidents.md)