Detecting Ci collisions (change)
On the current roadmap there is an item in design called:
- CHANGES
- Conflicts/Collision Detection
- Display collision/conflicts in the Change Details page when two changes have common CIs and contain overlaps in their schedules.
We'd like to request the collision/conflict logic also review the 'Services Affected' field. We do not use the CMDB - few are - and therefore are not defining the specific CI in the change. Instead we highlight the service that is impacted by the change (Example: Exchange (email) vs. serverxyz.123.rc). This way when we produce reports for the business, the language shown is clearly understood by them. The logic could behave the same in that it reviews changes that impact the same services and produces an error message.
I understand how the relationships could work but the amount of effort to initiate and maintain the CMDB is not sustainable for our team.