Two CABs/week- Preventing Approved Changes from CAB1 to be in CAB2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi All ...
We are setting up two CAB meetings per week (Monday & Thursday).
Our Monday CAB is for reviewing changes with a planned start Monday @ 17:00 through planned start Sunday 23:59.
Our Thursday CAB is for reviewing changes with a planned start of Thursday @ 17:00 through those starting Sunday @ 23:59.
So, all the changes in both CABs have Sunday 23:59 as their last possible planned start time.
Monday CAB ----------------------------------------------------------> Sunday 23:59
Thursday CAB -----------------> Sunday 23:59
So , let's say we have 3 changes in Monday's CAB:
CR 1 - planned start 19:00 Monday
CR 2 - planned start 16:00 Friday
CR 3 - planned start 23:00 Sunday
At the Monday CAB, we approve all of them for deployment at their planned start times.
We have two new changes for Thursday's CAB:
CR 1 - planned start 15:00 Friday
CR 2 - planned start 02:00 Saturday
I don't want any of the already approved CRs from the Monday CAB to show up in Thursday's CAB.
Without manually removing the Monday changes from the Thursday CAB agenda, is it possible to prevent those Monday CAB-approved changes from showing up in Thursday's CAB agenda?
We're on the Zurich release
Thanks in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Check this field in CAB meeting -- agenda builder
If that doesn’t work, then in Agenda Builder you should add a condition that only changes approved before a specific date (e.g., before XXXX) are included, so that newer changes do not appear in your Thursday CAB.”
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/dratulgrover [ Connect for 1-1 Session]
****************************************************************************************************************
