Change Conflicts

[lucsutherland]

I have found something within change management that I am unsure how to fix. I scheduled a change with CRM as the affected CI, and then scheduled another one with the same CI for the same time.

This generated two conflicts, both of Type CI Already Scheduled, for the CI CRM. The Change and Conflicting Change were the original and current change requests, with positions swapped. Redundant, but not really a problem.

I went to change the CI on the second change request to ServiceNow, but it still generates a conflict. It is of type CI Already Scheduled, where the Affected CI is CRM. However, the Conflicting Change is the current change, and the Change is the change with CRM as the CI.

I changed the Configuration Item; shouldn't this have zero conflicts now?

[Aditya Telideva]

Interesting: do you have this feature:

Enable automatic change conflict detection ?

Thanks,

aditya Telidevara

[lucsutherland]

Hi Aditya,

Yes, I have the conflict detection running automatically, and it updates the conflicts whenever I save the Change Request. But the behavior I expect is to have a conflict when I use the CI that has a separate change, and then no conflicts when I change it to a different CI. But it's reporting a conflict regardless.