Move Multiple Tasks
Multiple tasks can be moved simultaneously from the Edit Tasks screen. To move more than one task at a time, navigate to the Edit Tasks screen where you can select the tasks which you want to move. From the top burger menu you will see the option Move Tasks. Clicking this will launch the Move Tasks Screen.
Please Note: A maximum of 10 tasks can be moved at one time
From the Move Task Modal Window you must select the Target Runbook where you want the tasks to be moved to. This can be elsewhere in the current Runbook or to a completely different Runbook.
Once you have selected the Target Runbook you then have to select the Phase which the tasks are to be moved to, followed by the stage they should be moved into and lastly before which task in the Target Runbook they are to be moved to.
Retain Predecessors
When moving multiple tasks you have the ability to Retain Predecessor Tasks. Selecting this option means that tasks being moved that are linked to tasks which are not being moved are retained after the move occurs, as long as the tasks are not being moved into another phase of the current Runbook.
If you choose not to select this checkbox then when the tasks are moved, any predecessors outside of the suite being moved will no longer exist.
If there are any Predecessor Dependencies within the task grouping which is being moved, these will always be retained.
Retain Successors
You also have the ability to retain Successor Tasks. Selecting this option means that all tasks being moved that are linked to tasks not being moved are retained after the move. The only times these deps would not be retained is if the Tasks are being moved to another phase in the Runbook.
If you chose not to select this checkbox then when the tasks are moved, any successors outside of the suite being moved will no longer exist.
If there are any Successor Dependencies within the task grouping which is being moved, these will always be retained.
Retain Ownership
You can chose to retain the task ownership when moving tasks within the existing Runbook or to another Runbook. You can opt to retain both the Owner and the Team or one or the other.
If moving to a different Runbook, then check that the user actioning the move is a deployment manager in the Target Runbook. If they are then retain the ownership for owners and teams are added to the deployment team automatically.
If a user actioning the move is ONLY a team member and not a deployment manager then on moving the tasks, the owners/teams will be removed.
Retain Notes
If the Retain Notes checkbox is selected any notes which have been added to tasks will be retained regardless of the author of the note being part of the Deployment Team in the Target Runbook.
Retain Documents
If documents have been attached to tasks they too can be moved when tasks are being moved by selecting the Retain Documents checkbox.
