--- sourceDocument: xanadu Combined Product Files sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/delta-vancouver-xanadu Release : - yokohama ft:locale : - en-US ft:publication_title : - xanadu Combined Product Files ft:clusterId : - delta3xv bundleId : - delta3xv --- Combined Incident Management release notes for upgrades from Vancouver to Xanadu ================================================================================ Combined Incident Management release notes for upgrades from Vancouver to Xanadu {#ariaid-title1} ================================================================================================= * Release version: Yokohama * * Updated January 30, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Consolidated page of all release notes for Incident Management from Vancouver to Xanadu. How to use this page -------------------- To help you prepare for your upgrade, we have combined the cross-family Incident Management release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Vancouver to Xanadu. Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release." Important information for upgrading Incident Management to Xanadu ----------------------------------------------------------------- Before you upgrade to Xanadu, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-incidentmanagement-summary__entry__2} | Release | Release notes | |---------------|------------------------------| | Vancouver | No updates for this release. | | Washington DC | No updates for this release. | | Xanadu | No updates for this release. | [ ] New features ------------ Between your current release family and Xanadu, new features were introduced for Incident Management. {#dfrn3-incidentmanagement-summary__entry__10} | Release | Release notes | |---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Vancouver | [Enhancement to the major incident creation process](https://www.servicenow.com/docs/access?context=major-incident-trigger-rules&family=vancouver&ft:locale=en-US) : Control when to promote an incident to a major incident or propose a major incident candidate by using the Action to take field when defining the trigger rules for a major incident. By default, the base system activates a trigger rule that automatically promotes an incident with Priority value 1 to a major incident. | | Washington DC | [User role for read and write access to incident tasks](https://www.servicenow.com/docs/access?context=installed-with-incident&family=washingtondc&ft:locale=en-US) : Provide more read and write operation privileges in an incident task record to an agent with the sn_incident_task_assigned_user role. You must install and activate the ITSM Roles plugin (com.snc.itsm.roles) to use the base system ACLs related to this role. | | Xanadu | No updates for this release. | [ ] Changes ------- Between your current release family and Xanadu, some changes were made to existing Incident Management features. {#dfrn3-incidentmanagement-summary__entry__18} | Release | Release notes | |---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Vancouver | [Solution definition enhancements](https://www.servicenow.com/docs/access?context=predictive-intelligence-for-incident&family=vancouver&ft:locale=en-US) : Solution definitions now use the Description field in addition to the Short Description field to recommend similar incidents in an Incident record. A Machine Learning (ML) model enables the Description field in solution definitions to provide better quality results. The following solution definitions have been changed to include the Description field: * Similar Incidents * Similar Open Incidents * Similar Closed Incidents [Incident resolution behavior](https://www.servicenow.com/docs/access?context=resolve-and-close-an-incident&family=vancouver&ft:locale=en-US) : When you resolve an incident in Core UI by using the Resolve UI action or by setting the incident state to Resolved, the Resolve dialog box is displayed with resolution code and resolution notes. Note: This behavior is applicable only when the Now Assist for ITSM application is installed and the Resolution notes generation skill is activated. For information about Now Assist for ITSM, see [Configure Now Assist for IT Service Management (ITSM)](https://www.servicenow.com/docs/access?context=configure-now-assist-for-itsm&family=vancouver&ft:locale=en-US). | | Washington DC | No updates for this release. | | Xanadu | [Email notification link redirection behavior](https://www.servicenow.com/docs/access?context=t_ViewIncidentNotification&family=xanadu&ft:locale=en-US) : In email notifications, you can now decide where the links to an incident record are redirected. Instead of an incident record automatically opening in the classic UI16 interface in Incident Management, the incident record can be opened in SOW. The incident record link in an email notification opens in SOW only if the following conditions are met: * The Redirect SOW Email notification (sow_email_notification_redirect) system property is set to true. * The user selecting the incident record link has the sn_sow.sow_user role. The ITSM Notifications Redirection (com.snc.itsm.notifications_redirection) plugin is installed and activated automatically to support this behavior. To ensure consistency, the email notification template is updated to send the notification from SOW in the same format as sent from classic UI16 interface. Also, the template theme is updated to match the Next Experience theme. | [ ] Removed ------- Between your current release family and Xanadu, some Incident Management features or functionality were removed. {#dfrn3-incidentmanagement-summary__entry__26} | Release | Release notes | |---------------|------------------------------| | Vancouver | No updates for this release. | | Washington DC | No updates for this release. | | Xanadu | No updates for this release. | [ ] Deprecations ------------ Between your current release family and Xanadu, some Incident Management features or functionality were deprecated. {#dfrn3-incidentmanagement-summary__entry__34} | Release | Release notes | |---------------|------------------------------| | Vancouver | No updates for this release. | | Washington DC | No updates for this release. | | Xanadu | No updates for this release. | [ ] Activation information ---------------------- Review information on how to activate Incident Management. {#dfrn3-incidentmanagement-summary__entry__42} | Release | Release notes | |---------------|---------------------------------------------------------------------------------------| | Vancouver | Incident Management is active by default with the Incident plugin (com.snc.incident). | | Washington DC | Incident Management is active by default with the Incident plugin (com.snc.incident). | | Xanadu | Incident Management is a ServiceNow AI Platform feature that is active by default. | [ ] Additional requirements ----------------------- If any additional requirements were introduced or changed for Incident Management we have noted them here. {#dfrn3-incidentmanagement-summary__entry__50} | Release | Release notes | |---------------|------------------------------| | Vancouver | No updates for this release. | | Washington DC | No updates for this release. | | Xanadu | No updates for this release. | [ ] Browser requirements -------------------- If any specific browser requirements were introduced or changed for Incident Management we have noted them here. {#dfrn3-incidentmanagement-summary__entry__58} | Release | Release notes | |---------------|------------------------------| | Vancouver | No updates for this release. | | Washington DC | No updates for this release. | | Xanadu | No updates for this release. | [ ] Accessibility information ------------------------- Review details on accessibility information for Incident Management, such as specific requirements or compliance levels. {#dfrn3-incidentmanagement-summary__entry__66} | Release | Release notes | |---------------|------------------------------| | Vancouver | No updates for this release. | | Washington DC | No updates for this release. | | Xanadu | No updates for this release. | [ ] Localization information ------------------------ If there are specific localization considerations for Incident Management we have noted them here. {#dfrn3-incidentmanagement-summary__entry__74} | Release | Release notes | |---------------|------------------------------| | Vancouver | No updates for this release. | | Washington DC | No updates for this release. | | Xanadu | No updates for this release. | [ ] Highlight information --------------------- If there are specific highlight considerations for Incident Management we have noted them here. {#dfrn3-incidentmanagement-summary__entry__82} | Release | Release notes | |---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Vancouver | * Improve the prediction and recommendation of similar incidents with solution definition enhancements. * Control when to promote an incident to a major incident or propose a major incident candidate. See [Incident Management](https://www.servicenow.com/docs/access?context=c_IncidentManagement&family=vancouver&ft:locale=en-US) for more information. | | Washington DC | Manage the read and write access of agents using the sn_incident_task_assigned_user role. See [Incident Management](https://www.servicenow.com/docs/access?context=c_IncidentManagement&family=washingtondc&ft:locale=en-US) for more information. | | Xanadu | Control when an incident record link in the email notifications redirects to the incident record in Service Operations Workspace (SOW). See [Incident Management](https://www.servicenow.com/docs/access?context=c_IncidentManagement&family=xanadu&ft:locale=en-US) for more information. | [ ]