Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

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 (

Image omitted: icon-sr-reliability-tasks.png
Reliability tasks icon\).
  1. Select the Incidents tab.

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

    • 1 - Critical
    • 2 - High
    • 3 - Moderate
    • 4 - Low
    • 5 - Planning (default)
    • 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