Enable automatic change conflict detection
Automate conflict detection to run at specific intervals or when a change request is updated to immediately review the conflicts when the schedule dates are updated.
Before you begin
Prior to running conflict detection, consider the following scenarios:
CMDB list size and relationship complexities
If you have a large organization with a large CMDB, conflict detection can take longer to complete.
Inactive changes are not evaluated
Conflict detection does not evaluate inactive changes when determining conflicting changes.
Advanced mode conflict checking is disabled by default
When you upgrade the application, advanced mode conflict checking is disabled by default and affected CIs are not considered during conflict detection. To evaluate all CIs, set the mode to Advanced.
Role required: change_manager or admin
Procedure
Navigate to All > Change > Administration > Conflict Properties.
Select one of the following options.
| Run conflict detection automatically after changes to Configuration item, Planned start date, Planned end date, or State when a change request is updated | When selected, runs conflict detection automatically when a change to one or more of the following fields on the change request record is saved.- Configuration item - Planned start date - Planned end date - State |
| Enable the scheduled change conflict checker | When selected, runs the following conflict detection scheduled jobs at these intervals: Change Conflict Detection < 1 Week Away is scheduled every day. Change Conflict Detection < 1 Month Away is scheduled every two days. Change Conflict Detection >=1 Month Away is scheduled every seven days. |
Click Save.
You can view the conflicts on the Conflicts tab on the change request record.
Parent Topic:Conflict detection
Related topics
Create blackout and maintenance schedules in Change Management
Configure a change request to monitor outside maintenance schedule conflicts