Conflict detection and maintenance windows

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2022 02:43 PM
Can anyone confirm that the "repeat_until" date on a maintenance window should be considered when conflict detection runs on a change request? (meaning if the date is in the past then the maintenance window shouldn't be considered for detection.)
I am seeing that while this date will prevent the maintenance window from showing in the Conflict Calendar, a conflict record is still created and shows in the conflicts related list.
Scenario:
- A maintenance schedule is created for a specific CI (for change request)
- schedule is any Monday from 5-6pm
- the "repeat until" date on the schedule is 07-15-2022 (in the past)
- a change is created for the CI and scheduled for Monday 7-25-2022 7pm-8pm
- Conflict detection runs
- A conflict record is created for "Not in Maintenance Window" (not expected)
- The conflict calendar does not show the past maintenance window (expected)
Is this expected behavior? Also, if that date isn't considered, then how would you make a maintenance window inactive without deleting it?
Thanks for any insight!
- Labels:
-
Change Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2022 11:12 AM
I'm confused by your question. If you have an repeats until which is in the past. Why would you think it is not expected to get a "Not in maintenance window" record? This is what I would expect the results to be and that is what happened when I test this in my PDI. I created a Maintenance window for every Monday in July. Then I created a change to be Scheduled this Monday and I got a conflict.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2022 04:42 PM
Thanks Brian - yes, that does make sense from a schedule perspective. I should have added more context around my problem. Basically I have a requirement to be able to 'deactivate' a maintenance window schedule without deleting it. If a new window is added, or there's a decision to not use a window, there doesn't seem to be a way to prevent conflict detection from using the original window in its logic.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2022 08:14 AM
But if you are getting a conflict then to me it is not using that window anymore.