Conflict detection

Conflict detection identifies when changes are scheduled at the same time or impact the same configuration items (CIs) and related CIs. You can run conflict detection automatically or manually.

Conflict detection also highlights when a change occurs outside of the maintenance schedule or during a blackout schedule so that you can reschedule the change.

Conflict detection enables you to perform the following tasks.

Identify the recency of the conflict information
Conflict status and Conflict last run fields on the change request record enable you to identify whether conflict detection was run and the date and time it was last run.
Run manual and automated conflict detection
You can run conflict detection manually or automate it based on your requirements. Save the change request record prior to running conflict detection.
View conflict information
You can view conflict information in the Conflicts section of the Change Request form after you save the change request and run conflict detection. The Conflicts section provides information such as affected CIs, type of conflict, schedule, conflicting changes, and time and date details regarding when the conflict detection was last run.

Maintenance schedule management

You can assign maintenance schedules to configuration items and configure the Change Request form to show when a scheduled change to the CI is outside the schedule. In the Configuration application menu, navigate to the appropriate module. For example, to assign a maintenance schedule to a web server, navigate to Configuration > Web Servers and select the server. In the Maintenance schedule field, set the value to one of the configured maintenance schedules and save the CI.

Monitor changes outside the maintenance schedule

You can also configure the Change Request form to display the Outside maintenance schedule field. This check box is informational and indicates whether the planned start date and end dates for the change occur outside the maintenance window. The instance sets this value and disregards any user changes to this check box.

This field is set to true if either of the following actions occurs.
  • The planned start and end dates in the change with an associated CI are compared to the maintenance schedule and determined to be outside the schedule.
  • Affected CIs associated with the change request are checked against their assigned maintenance schedules, if any.
Note: Only the maintenance window for the primary CI or affected CIs are checked; the upstream and downstream CIs are not checked.

When you save a change request that is outside the maintenance schedule, a warning appears for each CI (primary or affected) that is outside the maintenance schedule, if the change request was previously not marked as outside the maintenance schedule.

You see a warning for each CI whose planned dates now fall outside the maintenance schedule.