A linked task is created using the linked task type. When a linked task is added to a runbook, it is linked to a template that is then converted to a linked runbook. In this article, we'll cover creating linked tasks, and linked tasks and templates.
Create a linked task
To create a linked task, follow the steps below:
Create a task.
Click the More options icon on the task > Insert Linked Task(s)
Select a template for the linked task in the pop-up modal. You have the ability to select any template you have access to (and is approved) within your workspace.
Select your linked task option and run style.
Click Link.
You can also add a linked task via the task details panel. Read more about this method here.
Linked tasks and templates
Templates are an important aspect of creating linked runbooks; when creating a linked task, you will need to select a template. The selected template will form the newly created linked runbook, while the attached runbook becomes the parent runbook.
It’s important to note the difference in behavior for linked tasks in parent templates and parent runbooks:
Parent templates: If a linked task is created in a parent template, the task will remain linked to the template, allowing the template to be reused indefinitely.
Parent runbooks: If a linked task is created in a parent runbook, the task will immediately convert the linked template to a linked runbook, making it unique to the event.
Additional things to note are as follows:
Linked tasks will always be associated with the template a linked runbook is created from.
When a linked task is copied and pasted, new linked tasks will be created from the template associated with the original linked task.
If a template associated with a linked task type is changed or if a linked task is deleted, the template will no longer be associated with the linked task.
When a runbook is created from a template, all linked task templates are converted to runbooks, ultimately linking the linked tasks to the newly created runbook.
If a parent runbook is marked as a template, all linked tasks will then link back to their original templates. Any previously created runbooks from those linked tasks will be archived.
Linked task type options and settings
Linked is the default linked task type option that can be selected when creating a linked task type. You also have the ability to add more custom task type options to your Cutover instance depending on your needs.
The default linked task option becomes ready to start when all dependencies are met. In the associated linked runbook, you are able to start the linked task in the parent runbook or linked runbook. Either selection will initiate the task start in the parent, which will start the linked runbook.
With custom task options, you have the ability to use Cutover's existing features, such as auto start. If auto start is added to a linked task, the linked task and linked runbook will start automatically when all dependencies are met.
Create linked tasks in bulk
To add linked tasks in bulk, follow the steps below:
Click the More options icon on the task you'd like to create linked tasks in bulk from.
Click Insert linked task(s).
Select multiple templates in the template selection modal. You have the ability to select any template you have access to within your workspace. Each template selected will create one linked task.
Use applicable filters to select the appropriate templates.
Next, select a linked task type and run style.
Select linked task type: If you have more than one available linked task type in your workspace, select the task type most suited to your needs.
Select run style: Decide whether your linked tasks will be inserted in sequence or parallel. If sequence is selected, linked tasks will be inserted with dependencies in the order templates were selected in the previous template selection modal (from Step 3). If parallel is selected, linked tasks will be inserted to start at the same time.
Click Link.
All linked tasks will be inserted directly below the original tasks they were created from.
Related articles
Read more about linked runbooks: