Skip to content

Task Templates ​

Table of Contents


Why templates exist ​

Templates let you avoid repeatedly filling in the same fields when creating similar tasks. They are especially useful in recurring processes — such as onboarding a new campaign, a periodic data review, or regular reports. A template stores a predefined task structure: title, description, priority, status, labels, and subtasks.


Creating a template from an existing task ​

A template can be created in two ways:

  1. From an existing task — by copying/duplicating a task as a template (option available from the task context menu). The new template inherits all fields from the original.
  2. From scratch — by directly creating a new template in the template library.

Templates are technically tasks of a special type and are stored in the template library, accessible from the Tasks tab. Templates can be organized into template groups, which make navigation easier in a large library.


Template scope ​

Templates are created in the context of a workspace and are available by default to all users of that workspace. A template linked to a specific project is visible within that project's context.


What gets copied when applying a template ​

When applying a template to a task, the following fields are transferred:

FieldCopied?
TitleYes
DescriptionYes
PriorityYes
StatusYes
LabelsYes (fully replaces labels on the target task)
SubtasksYes (recursive cloning of the entire subtask tree)
AssigneeNo
Due dateNo
Project / sectionNo (retained from the target task)

Example use cases for templates ​

  • Campaign onboarding — template with subtasks: account configuration, feed verification, budget setup, campaign structure review, activation
  • Product feed review — template with a checklist: download error report, analyze rejected products, fix attributes, re-sync
  • Monthly report — template with a predefined report structure, priority, and labels for the relevant department