---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Update the priority of an SRM incident

# Update the priority of an SRM incident {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

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

## Before you begin

Role required: Responder, Manager, or Administrator

## Procedure

1. Navigate to WorkspacesService 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 (![Reliability tasks icon]()). {#sr-update-incident-severity__select-reliability-tasks}
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)
   {#sr-update-incident-severity__choices_emy_cs5_1pb}
5. Select OK.  
   The new priority is reflected in the incident list view and incident header and form field.
{#sr-update-incident-severity__steps_dfp_sr5_1pb}

*[\>]: and then