Skip to main content
Add Tasks to a Runbook

Learn how to add tasks to a runbook.

Cutover Documentation Team avatar
Written by Cutover Documentation Team
Updated over 3 months ago

Tasks carry out and help execute a variety of events —such as resilience testing, cloud migration, and platform implementation — and make up the entirety of a runbook. In this article, we'll cover how to create and add tasks to a runbook.

Add tasks


Runbooks consist of a set of tasks that are created to carry out a specific set of functions in a runbook. Tasks can be added to a runbook at any time. In a new runbook, you will automatically be prompted to add a task:

Enter a name for your task and hit Enter — your task will be created in the Primary stream.

To add additional tasks, hover over your initial task and click the plus icon.

Another prompt will populate — enter a title for your task and hit Enter.

Create task


Click + Create task above your task list.

Enter a title for your task, and hit Enter to create. Your task will be added to the top of your task list.

Task dependencies


As tasks are added, by default, they are added in sequence, taking the previous task as a predecessor. This sequence of tasks can be edited, adding more complexity to the plan by selecting a task and expanding the Dependencies section of the Edit Task panel. It is also possible to bulk select multiple tasks and add a predecessor.

To change a task's predecessor, click the task to edit it. Next, follow the steps below:

  1. In the Dependencies section, click the x icon to remove any current predecessors.

  2. Add a new predecessor by typing the task name or task ID.

Changing a task's predecessor will then change the order of the tasks in your runbook.

Note: Successors of a task cannot be moved. Additionally, it cannot be moved if a task has more than one predecessor.

Task shortcuts


Use the following shortcuts to save time when adding tasks:

  • Hit Enter after adding text to a task to save it.

  • Add task duration by typing directly into the task box using day, hour, minute format. For example, 1d2h20m.

  • Enter the $ symbol to select a stream for your task.

  • Display task type options by entering the ^ key in the task box.

  • Assign teams and users to a task by entering the @ symbol in the task box.

  • Hit Enter after creating a task to populate a new task directly beneath it. Subsequent tasks will be created in sequence in the same stream as the prior task.

Click View shortcuts for a list of additional shortcuts when adding a task.

Edit tasks


Selecting a task automatically displays the task detail panel to the right of the task list, where the task details can be viewed and edited. Selecting the task again collapses the panel.

If a task has not yet started and the runbook is in planning mode, or paused, or while in run of a dynamic mode runbook, you can update the following within the Task detail panel:

  • Title: Edit the name of your task.

  • Task Type: Select another task type option if needed.

  • Stream: Select which stream your task is in.

  • Level: Select a level of importance for your task. To note, the levels provided are for personal preference and don't carry a specific value.

  • Duration: Set or edit task duration. Add a fixed start time or scheduled auto finish.

  • Custom Fields: Related custom fields will appear in this area.

  • Description: Add a description for your task. Task descriptions can also be used to provide task executors with helpful information or additional context on the task they are executing. There is no character limit for a task level description. Any hyperlinks added in here will display the full url link when clicked on. It won't open the url but it will allow you to edit it.

  • Assigned Users & Teams: Add or edit users and teams assigned to your task.

  • Dependencies: Update task dependencies (predecessors and successors).

  • Advanced settings: Update start and end requirements, and disable task notifications if needed.

  • Other details: View who created the task and when.

  • Webhooks - Incoming: Any webhooks associated with the task will be here.

If a task state is in progress but the runbook is in planning mode, or paused, or while in run of a dynamic mode runbook, you can update the following within the Task detail panel (based on the list above):

  • Title: Edit the name of your task.

  • Duration: Set or edit task duration. Add a fixed start time or scheduled auto finish.

  • Assigned Users & Teams: Add or edit users and teams assigned to your task.

  • Description: Add a description for your task. Task descriptions can also be used to provide task executors with helpful information or additional context on the task they are executing. There is no character limit for a task level description. Any hyperlinks added in here will display the full url link when clicked on. It won't open the url but it will allow you to edit it.

  • Custom Fields: Related custom fields will appear in this area.

If a task state is completed no changes can be made.

Note: For further information about runbook modes, please see the Related Articles section at the end of this article.

Bulk edit tasks


Note: Only the Runbook Admins or Stream Editors have permission to bulk edit tasks.

You can bulk edit tasks by selecting multiple tasks or using the select all option:

With bulk editing, you can delete, duplicate, or create a snippet from multiple tasks.

Bulk actions when in planning or pause mode include edit selected, copy and paste, and task deletion. Bulk actions when in run include task skip.

Scheduled auto finish


Task types that do not have task end requirements, aren’t integration task types and are not auto-finish task types, can have a scheduled auto finish.

To note, these tasks can still be executed manually or skipped. Once this option is selected, the task will automatically finish when its duration has been reached.

Scheduled auto finish is calculated by the start date and time of the task, in addition to duration. Validation checks are performed when tasks are set for scheduled auto finish. If a scheduled auto finish fails, the runbook audit log will document this occurrence.

Related articles


For more information about runbook modes, see the links below:

Did this answer your question?