Detecting conflicts by using the Calendar
Before you begin
To access collision management functionality, you must have the required permissions. For more information, see Roles-and-permissions-in-Change-Management.
To detect collisions and take action on them
The Calendar detects collisions after services or CIs are related to a change request, and the scheduled dates have been specified. Potential collisions are displayed when you are creating or updating the change request and after you save the change request.
The following video (2:28) describes the process of detecting collisions and taking action on them:
When you create a change request, after you enter values for the scheduled start and end dates, but before you save the change request, the list of collisions (if any) for services or related CIs are displayed when you click on Check collisions at the bottom of the screen.
In the Change collisions window, you can see the Change ID, Summary, CI Name, Status, and the change coordinator name. Click the Send an email to all change coordinators with conflicting CRQs link to contact the change coordinators by email, in case you need to discuss schedules and priorities.
After you save the change request, if the collision is not resolved, the system warns you again about potential collisions by displaying an alert banner at the top of the change request details. To resolve the collisions, click Show more to display the Change collision window.
To change the status of the collisions, select the impacted Change ID or all the Change IDs and select the required option from the Mark selected list.
In the Change collisions window, click Calendar to view the collisions in a flexible calendar view that displays collisions in the current day, week, or month. You can click to view the list of collision tickets in a side bar. The number of collisions are mentioned next to the pills for each collision ticket. You can drag a ticket to adjust the start and end dates of the ticket directly in the Calendar. You can also drag and drop a ticket to new dates in the Calendar.
The Business Events and Outages are also shown in the Calendar along with the collisions. You can use the filter in the calendar to show the relevant Business Event, Outage or Change.
For more information about using collision statuses as a change manager or change coordinator, see Detecting-collisions-between-change-requests.
How collision statuses are stored
A single collision status record is shared by both the current change request and the change request that is in collision. If one person performs an action on the collision from either change request, the status and rationale (if any) are visible in both change requests. You can provide a rationale when you update the collision status.
Instructions for classic interfaces