Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
This property enables or disables conflict checking for change requests that overlap in timing, allowing for more flexible scheduling of changes. |
| What area does it affect? |
Change Management |
| What does the default mean? |
The default value is "true", which means this behavior is enabled by default. |
| When should you review it? |
Review this property when adjusting change request scheduling policies or resolving conflicts. |
Out of the box property record
Raw metadata from the property record.
| Property name |
change.conflict.allow_contiguous_changes |
| Sys ID |
444f6869532333008ef67c2c0fc5876d |
| Type |
boolean |
| Application |
Global |
| Default value |
true |
| Description |
When conflict checking for similar change requests (by Affected CIs or Assigned to) find records that overlap with the current change request only.
Old behavior did not allow change requests that start at the same time as the end time of the current change request or a change request that ends at the same time as the start time of the current change request.
As an example the following change requests apply to the same configuration item.
CHG01, start: 2019-01-01 03:00:00 end: 2019-01-01 04:00:00.
CHG02, start: 2019-01-01 04:00:00 end: 2019-01-01 05:00:00.
If this property is set to true these contiguous change requests will not conflict, if the property is set to false they will conflict. |
| Updated |
2024-05-25 05:09:56 |
Sources
Related properties