Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Detect change conflicts automatically

Log in to subscribe to topics and get notified when content changes.

Detect change conflicts automatically

You can automate conflict detection to run at specific intervals or when a change request is updated.

Before you begin

Prior to running conflict detection, you must consider the following scenarios unique to your organization.
CMDB list size and relationship complexities
If you are a large organization with a large CMDB, conflict detection might 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 switched off by default
When you upgrade, advanced mode conflict checking is switched off by default. Hence, affected CIs are not considered during conflict detection. In order to evaluate all the CIs, set the mode to Advanced.

Role required: admin or change_manager


  1. Navigate to Change > Administration > Conflict Properties.
  2. Select one of these options.
    Run conflict detection automatically after changes to Configuration item, Planned start date, Planned end date or State when a change request is updated Runs conflict detection automatically when a change to one or more of the following fields is saved.
    • Configuration item
    • Planned start date
    • Planned end date
    • State
    Enable the scheduled change conflict checker Runs conflict detection 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 7 days

  3. Click Save.
    You can view the conflicts in the Conflicts tab on the change request.