Cloning a Runbook
Any Runbook can be very quickly cloned and new details added. Anyone but a Participant User can use this functionality.
When a Runbook is cloned it will be cloned into the same Group, Programme, Project, Service and Environment as the original Runbook. However these attributes can be changed once the Clone is complete.
Cloning the Runbook
Click on the 'Clone ' from the Runbook More Options menu.
Provide a name for the new Runbook and indicate which features you would like to retain.
You can choose to Retain the Source Default Deployment Manager which ensures the source Deployment Manager is kept or choose to Replace, which removes the Source Deployment Manager. In either scenario, the person cloning will automatically become the Default Deployment Manager for the new Runbook.
You can also retain the Team which the Runbook, this will keep all Team Members in the Runbook.
Retaining Skipped Tasks will keep any tasks which have previously been skipped. Not checking this box will return task to their original state before they were skipped.
Selecting to Use Planned Times will clone the Runbook with the original Task duration's aligned to Tasks rather than the time the Tasks took to complete in activated Runbook.
By choosing to clone Notes and Docs the newly cloned Runbook will retain any documents and notes which were added to the original Runbook
Select the Clone button as above to clone your Runbook Once cloned this will appear in the List Runbook's screen.
Please note: If you clone a Runbook with no Schedule then the Explicit Start Times will not clone over.
Cloning a Runbook with a Schedule will result in the new Runbook being in a state of Construction.
Cloning a Runbook without a Schedule will result in the new Runbook being in a state of Initial.
Clone the Runbook and Retain Schedule
When selecting to Clone the Schedule of the Runbook another box will appear for you to enter a New Start Time. From the New Start Time that has been entered the times from the original Runbook will be off set.
If the Runbook has been scheduled and you have an explicit start time of 2 hours from the Change Start, then when you clone the Runbook and enter a new schedule, the explicit start time will still be 2 hours from the new Change Start time.
Please note that if you have explicit start times these will remain as explicit but will be offset as per your clone's new scheduled start time.
Clone An Initial Runbook
If you choose to clone Explicit Start Times of a Runbook in the state of Inital, you will be prompted to enter a Plus/Minus Offset. As the Runbook hasn't been scheduled, ICEFLO requires you to enter an offset in relation to the current explicit start times in the Runbook you are cloning from. If the explicit start time was 23rd June 13:00 and you offset it by + 1 day then the explicit start time in the newly cloned Runbook would be 24th June at 13:00.
Clone External Dependencies
By selecting to clone a Runbook without external dependencies, you can enter a new Runbook name in the field provided.
When selecting to clone a Runbook and retaining external dependencies all Runbooks which are linked via external deps are also cloned. The Cloned Runbooks will retain their original titles.
