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

SRM incidents

Track and collaborate on incidents in the Incidents tab, helping you and your teams resolve issues efficiently.

The Incidents tab appears in the Service Reliability Management (SRM) Reliability tasks page. Its top header shows description information, tags, priority information, state, service, and assignment group.

Note: Tags are imported from third-party integrations and attached to incidents. However, you can also create tags to categorize data and drive system logic using the Tag icon

Image omitted: icon-sr-tag.png
Tag icon. For more information on creating and viewing tags, see [Manually create SRM tags](sr-create-tags.md).

When selecting an incident, you're taken to an overview. This section contains three content panels: Summary, Activity, and Recommended actions.

Note: When an editable field is updated, notifications are sent based on user notification preferences.

In the Impact Summary, you find the following information:

FieldDescription
Configuration itemName of and link to the configuration item associated with this incident.
FieldDescription
Configuration itemName of and link to the configuration item associated with this incident.
Managed byTeam responsible for the incident.
Owned byIncident owner.
Approval groupTeam responsible for approvals.
LocationGeographical location of the incident if defined.
Operational statusStatus of the incident.
Manually added.Whether this incident was manually added or the result of an error budget policy.
FieldDescription
Short descriptionBrief description of the incident.
DescriptionDetailed description of the incident.
NumberIncident identifier.
ImpactImpact is a measure of the effect of an incident on business processes. Choices are: - 1 - High - 2 - Medium - 3 - Low
Assignment groupTeam assigned to the incident.
Priority

Priority is based on Impact and Urgency, and it identifies how quickly the incident should be addressed. Choices are:

  • High Impact = Critical Priority
  • Medium Impact = High Priority
  • Low Impact = Moderate

Note: See Priority Data Lookup rules below.

CategoryCategory of the incident. Choices are: - Inquiry/Help - Software - Hardware - Network - Database
UrgencyUrgency is a measure of how long the resolution can be delayed until an incident has a significant business impact.
ServiceAffected service associated with the incident. You can edit this field from a list menu.Note: When you set a service, and that service has an assigned team, the assigned team of that service is automatically assigned to the incident.
SeverityImported severity on the incident. Values P1–P5.
Configuration itemAsset associated with the incident.
Assigned toIndividual responsible for resolving the incident.
StateState of the incident. The state moves and tracks incidents through several stages of resolution.Choices are: - New - In Progress - Ob Hold - Resolved - Canceled
Watch listIndividuals interested in the incident. Subscribes them to notifications according to their preferences.
Resolution codeCode associated with the resolution.Choices are: - None \(default\) - Duplicate - Known error - No resolution provided - Resolved by caller - Resolved by change - Resolved by problem - Resolved by request - Solution provided
Resolution notesDetailed information on the resolution. Resolution notes are posted to the Activity timeline.

Note: Priority is calculated according to the following sample data lookup rules:

ImpactUrgencyPriority
1 - High1 - High1 - Critical
1 - High2 - Medium2 - High
1 - High3 - Low3 - Moderate
2 - Medium1 - High2 - High
2 - Medium2 - Medium3 - Moderate
2 - Medium3 - Low4 - Low
3 - Low1 - High3 - Moderate
3 - Low2 - Medium4 - Low
3 - Low3 - Low5 - Planning

When a service is deleted, its integrations, alerts, incidents, and automations are removed. Deleting a service isn't a recoverable action so consider deactivating the service instead.

The Related Records tab contains any alerts associated with this incident.

Note: All field values are imported from the related records and aren't editable from SRM.

FieldDescription
NumberIdentifier for the related incident.
Short descriptionBrief description of the related incident.
PriorityPriority of the related incident.
StateState of the related incident.
Assigned toTeam member assigned to the related incident.
Assignment groupTeam assigned to the related incident.
ServiceService associated with the related incident.
FieldDescription
NumberIdentifier for the related alert.
SeveritySeverity of the related alert.
Short descriptionBrief description of the related alert.
AcknowledgedWhether the related alert has been acknowledged or not.
Assigned toTeam member assigned to the related alert.
Configuration itemAsset associated with the related alert.
ParentPrimary alert associated with the related alert.
FieldDescription
NumberIdentifier for the related changes associated with this incident.
Short descriptionBrief description of the related changes associated with this incident.
TypeType of the recent changes associated with this incident.
StateState of the recent changes associated with this incident.
Planned start dateDate and time to begin changes associated with this incident.
Planned end dateDate and time to begin changes associated with this incident.
Assigned toTeam member responsible for the change request associated with this incident.
FieldDescription
Short descriptionBrief description of the change request associated with this incident.
TypeType of the change request associated with this incident.
StateState of the change request associated with this incident.
Planned start dateDate and time to begin change request work associated with this incident.
Planned end dateDate and time change request work associated with this incident ended.
Assigned toTeam member responsible for the change request associated with this incident.

Postmortem tab

About Postmortem owner:

  • If a Scribe has already been chosen in the Collaboration panel Responders list, they're automatically made the owner.
  • If there's more than one scribe, the first one assigned is chosen. Otherwise, you can select an owner from the list menu.
  • If a new scribe is added or an existing user persona is changed to Scribe, that user is made the owner.
  • If you manually remove an owner, no new owner is automatically selected.

Use the drag-and-drop feature to edit postmortem sections. You can exclude sections from PDFs, delete sections, or reorder sections.

To add new sections, select the Add icon

Image omitted: icon-sr-add.png
Add icon..

Compose panel

Work notes are added to the Activity timeline automatically. Visible to responders and above. Add comments using the Compose text box.

Comments are added to the Activity timeline automatically. Visible to everyone in SRM.

Activity section

Stream that contains all the system activity, and resolution notes. You can filter, sort, expand or collapse all posts using the header icons.

Image omitted: icon-sr-activity-header.png
Header icons.

Note: The filter option includes Post types, Field changes, and Filter sets. All choices are selected by default. Flagged entries are either all or none.

Image omitted: sr-incident-timeline-options.png
Activity section showing selected filters

Actions panel

Note:

The Notifications, Agent assist, Expert on-call, and Email templates panels aren't currently supported in SRM.

Attachments section

Open the Attachments section using the Attachment icon

Image omitted: icon-sr-attachment.png
Attachment icon.

On the Attachments section, you can initially Browse your local hard drive for files.

Once you have added attachments, you can:

  • Search for an attachment based on its name or extension

    Note: You must have two or more attachments to search.

  • Upload a new attachment using the (

Image omitted: icon-sr-add.png
Attachments\) icon.
  • Download, remove, or rename existing attachments using the More actions icon (
Image omitted: icon-more-options.png
More actions icon.\).

Template section

Open the Template panel using the Template icon

Image omitted: icon-sr-template.png
Template icon.

Note: Existing templates are displayed, but creating templates isn't available in SRM.

Collaboration panel

Displays the available Zoom meetings, Microsoft Teams, or Slack channels to start or join.

To start or join a Zoom meeting:

Note: The Zoom integration and recognized IDs must be active in your instance. If Start Channel is unavailable, contact your administrator.

  1. Select Start Zoom.

    • A meeting pop-up appears.
    • Add participants.
    • Select Create Meeting.
    • The meeting is created, invitations are sent, and you join the meeting.

      Note: Any issues found when starting a meeting are shown in a banner message.

  2. Select Join Meeting

    • Sign in to your Zoom account.
    • You join the Zoom meeting.
  3. Select Start Channel.

    • Sign in to your Microsoft Teams account.
    • Select Create. You are redirected to the Microsoft Teams application.
    • Back in the Collaboration column, the Join Channel button is activated.

      Note: Any issues found when joining a channel are shown in a banner message.

  4. Select Join Channel in the Collaboration panel in SRM.

  5. Sign into your Microsoft Teams account.

    You are taken to the channel in Microsoft Teams.

Start or join a Slack channel:

Note: The Slack integration and recognized IDs must be active in your instance. If Start Channel is unavailable, contact your administrator.

  1. Select Start Slack.

    • Add participants in the Create a Slack channel pop-up.
    • Select Create. You are redirected to the Slack application.
    • Back in the Collaboration column, the Join Slack button is activated.

      Note: Any issues found when starting a channel are shown in a banner message.

  2. Select Join Channel in the Slack application window.

  3. Sign into you Slack account.

    You are taken to the Slack channel.

Parent Topic:Exploring Service Reliability Management