--- sourceDocument: Xanadu IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/it-operations-management Release : - xanadu ft:locale : - en-US ft:publication_title : - Xanadu IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Working with Incidents in SRM # Working with Incidents in SRM {#ariaid-title1} * Release version: Xanadu * * Updated August 1, 2024 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read Plan ahead of service disruptions and have SRM send notifications and create status when incidents occur. Distractions are minimized and teams stay focused on remediation. You can manually create incidents within SRM or create an error budget action to do so. See [Manually create an SRM incident](https://www.servicenow.com/docs/jHIMrZ9ksxZPEhIxOWC6Tg "Create an incident if you think an issue poses a serious risk and should be taken care of as soon as possible.") or [Create SLO, SLI, and Error budget policies](https://www.servicenow.com/docs/LoNkMublsb9McVKQU7u1Zg "Create SLO, SLI, and Error budget policies to help you and your team track your service health and take the necessary actions when required.") for more information. * [Manual creation from an alert](https://www.servicenow.com/docs/TePtOq7TrhZMUK1gD1wlhw "Promote an alert to an incident if you think the alert poses a serious issue and must be taken care of as soon as possible.") * [Manual creation from the incident view](https://www.servicenow.com/docs/jHIMrZ9ksxZPEhIxOWC6Tg "Create an incident if you think an issue poses a serious risk and should be taken care of as soon as possible.") * Automatically from Alert automations, if Alert automations are installed. {#sr-work-incidents__ul_dcc_dq2_v4b} The Assigned to field on an incident specify who should be notified. When a team is selected as a responder, team automations are checked to determine which schedule to use for the notifications. Note: The Assigned to field is cleared when the Assigned-team or Service field is updated on an incident. Escalation policies for the newly assigned teams run. The field remains cleared until a user on the new team acknowledges an escalation notification. If the Service is changed and the new Service does not have an assigned team, no changes occur. When a Service is deleted, its integrations, alerts, incidents, and automations are removed. This is not a recoverable action so consider deactivating the service instead. Responders and above are notified for updates to incidents based on their notification preferences. If you made the update, you won't be notified. You can resolve incidents by selecting specific incidents or in bulk. See [Resolve an SRM incident](https://www.servicenow.com/docs/ziICrpoCMGcIPPvA7Xu_TQ "Resolve an incident, if you need it reviewed, or you think it has already been handled, but aren't ready to close it."), or [Close an SRM incident](https://www.servicenow.com/docs/cA3_VvX3cSMs3J6SDvdkSA "Close an incident, if you think it is not an issue, or if it has already been handled.") or [Cancel an SRM incident](https://www.servicenow.com/docs/JSOfcbDFk0PuP_VX8dXiFw "Close an incident, if you think it is not an issue, or if it has already been handled."). Note: Incidents in the Resolved state are automatically closed after 3 days. For more information on the areas and fields available in an incident, see [SRM incident workspace](https://www.servicenow.com/docs/Kou_1LhUopNEX1s2upH2OQ "The incident workspace contains various panels containing incident details and possible actions."). [Export list information to a file](https://www.servicenow.com/docs/sGNKp9LylvHtvERuUGLI6A "You can export live information to a file in SRM.") from the list view. Respond to an incident in the following ways: * [Tag an incident](https://www.servicenow.com/docs/1EvIHAbXyNo1DfZ25SMBhA "Tags help you classify and categorize data, or otherwise add information there isn't a field for. SRM imports tags and attaches them to services, alerts, and incidents. However, you can also create tags manually."). * [Update the priority of an SRM incident](https://www.servicenow.com/docs/0wICIdrOIJ_7RKa45ym7uw "If the priority of an incident should be changed, you can manually update it to reflect its new criticality."). * [Set the state of the incident](https://www.servicenow.com/docs/62d_hBBgjA6pWl6UWPa7VA "Incidents can be in a few different states depending on how they are acted on."). * [Copy an SRM incident](https://www.servicenow.com/docs/kOBy8rxzfGFsWEg9QfcpBw "Copy an incident, if you have a similar issue."). * [Add a service to an SRM incident](https://www.servicenow.com/docs/bSeg70awbkyWT4JCecx8YA "Add a service to an incident to increase the amount of data for the incident."). * [Add work notes to an SRM alert](https://www.servicenow.com/docs/RL3OeUxfQ0WVDATOkEeucw "Add work notes to an alert that are visible to all members of the alert team."). * [SRM incident workspace](https://www.servicenow.com/docs/Kou_1LhUopNEX1s2upH2OQ "The incident workspace contains various panels containing incident details and possible actions."). * [Resolve an SRM incident](https://www.servicenow.com/docs/ziICrpoCMGcIPPvA7Xu_TQ "Resolve an incident, if you need it reviewed, or you think it has already been handled, but aren't ready to close it."). * [Cancel an SRM incident](https://www.servicenow.com/docs/JSOfcbDFk0PuP_VX8dXiFw "Close an incident, if you think it is not an issue, or if it has already been handled."). * [Close an SRM incident](https://www.servicenow.com/docs/cA3_VvX3cSMs3J6SDvdkSA "Close an incident, if you think it is not an issue, or if it has already been handled."). * [Reopen an SRM incident](https://www.servicenow.com/docs/kd0JMVlZyhnIBoMlqGXxpQ "Reopen a closed incident if you think the issue is not yet resolved."). {#sr-work-incidents__ul_u52_rlr_tnb} * **[Manually create an SRM incident](https://www.servicenow.com/docs/jHIMrZ9ksxZPEhIxOWC6Tg)** Create an incident if you think an issue poses a serious risk and should be taken care of as soon as possible. * **[Reassign an SRM incident](https://www.servicenow.com/docs/hyWyhugHO0GjJBTAmLUuSA)** Reassign an incident to a responder when the incident tasks should be addressed by a particular team member. * **[Update the priority of an SRM incident](https://www.servicenow.com/docs/0wICIdrOIJ_7RKa45ym7uw)** If the priority of an incident should be changed, you can manually update it to reflect its new criticality. * **[Add a service to an SRM incident](https://www.servicenow.com/docs/bSeg70awbkyWT4JCecx8YA)** Add a service to an incident to increase the amount of data for the incident. * **[Add resolution code and notes to an SRM incident](https://www.servicenow.com/docs/V8t2FXUiorYe_nkm96h2PQ)** Add a resolution code and notes to an incident when you have resolved the incident. * **[Copy an SRM incident](https://www.servicenow.com/docs/kOBy8rxzfGFsWEg9QfcpBw)** Copy an incident, if you have a similar issue. * **[Resolve an SRM incident](https://www.servicenow.com/docs/ziICrpoCMGcIPPvA7Xu_TQ)** Resolve an incident, if you need it reviewed, or you think it has already been handled, but aren't ready to close it. * **[Cancel an SRM incident](https://www.servicenow.com/docs/JSOfcbDFk0PuP_VX8dXiFw)** Close an incident, if you think it is not an issue, or if it has already been handled. * **[Close an SRM incident](https://www.servicenow.com/docs/cA3_VvX3cSMs3J6SDvdkSA)** Close an incident, if you think it is not an issue, or if it has already been handled. * **[Reopen an SRM incident](https://www.servicenow.com/docs/kd0JMVlZyhnIBoMlqGXxpQ)** Reopen a closed incident if you think the issue is not yet resolved.