Issue:
When adjusting "Days After Patch Tuesday" schedules after Patch Tuesday but before the scheduled run date, the system automatically shifts the run date to the following month upon saving. This behavior presents challenges for us, particularly when patching issues arise, and we need to delay patching by a day or two without deleting or recreating schedules. Managing this manually across our large number of host pools is cumbersome and prone to human error, despite the simplicity of adjusting the day count.
Proposed Solution:
Allow schedule changes to remain within the current month as long as the initial run date has not yet passed. If a user wishes to move the schedule to the following month, they could use the "Start Date" field for this purpose.
This adjustment would streamline schedule management and improve automation by reducing the need for repetitive, manual adjustments. Given that this is based on a monthly fixed date, it may have been overlooked in testing, but implementing this would significantly enhance efficiency for our organization.
Comments (2 comments)