Change Freeze

[nasimg]

We have critical times that require no changes be carried out on major systems, we verbally tell the analysts there is a "change freeze", is there a way we can add this into the change schedule to alert staff to these times. It should stop them selecting these times for their changes.

[James Ainsworth]

Hi @nasimg

Thanks for your post.  It sounds like you are looking to be able to block out times within the change calendar where absolutely no changes can be scheduled for which would then result in the scheduling action item in a request to respect these dates and not allow changes to be schedule during this time?  We have also had ideas for having calendars on services and assets to allow for change freezes just against these particular items.

This is not currently available.  It is part of our longer term goals but we can see if there is something we can help with to work toward this functionality and give you something that you can work with sooner.

Are there any exceptions such as allowing emergency changes to take place during these periods?  Do you need this to apply globally to all services when a change freeze is put in place?  Possibly the inclusion of a flag for services and assets if they fall under change control.

Regards,

James 
 

[nasimg]

Don't worry its not high on my list of priorities - but yes it would have been a global setting ( and allowing emergency changes)

[James Ainsworth]

A new feature has been made available which will allow you to block out days within the Change Calendar as Freeze Periods.

A user with the appropriate rights can add to the Freeze Periods.  Once a Freeze period has been set, this can be applied to BPM Operations that automatically raise changes, and to the Scheduling Action on a request where it will prevent users from scheduling during a Freeze Period.

For more information please see our documentation here.

Regards,

James