A task template can be used in two ways: You can create a brand new task directly from a template, or You can apply a template to an already existing task. To learn how to create, edit, or lock templates, see the article Managing Task Templates.
Creating a new task from a template
- In (task) list views and (task) board views, several optional add buttons marked with a down arrow are available - in the top-level list, at task level, at subtask level, and above every column in the board's add area.
- At one of these spots, select not the
+, but thedown arrownext to it. - In the menu that opens, You'll find pinned templates under the heading
Templates. Alternatively, use✨ Browse templatesto search all templates in the workspace. - Select a pinned template directly, or select a template from the template manager, to create a new task directly with the selected template.
Note
If You instead select + Add task, an "empty" task is created without a template - unless a default template is defined at project or folder level. In that case, it is applied automatically. Default templates at folder level are defined in the Folder properties, and can be defined there separately for main tasks and subtasks. However, if You deliberately select a different template when creating the task, that one is used instead - the default template only applies when no explicit selection is made.
Applying a template to an existing task
- Open the desired task and click the
✨icon. - Select
✨ Browse templates. - Search for a template from the workspace.
- Click
Use templateto apply the template directly to the open task. Or click a template row to learn more about the template. - In the next step, You can decide which fields from the template should be applied to the open task. Select
Import everythingorCustom. UnderCustom, You can pick the specific fields and values to be applied from the template. - Enable the
Overwrite valuestoggle if existing field contents (e.g. a date) should be overwritten. If the toggle is disabled, field contents present in the template are ignored.
Note
As long as the Overwrite values toggle is disabled, fields that are already filled in are generally ignored when applying a template - regardless of whether the task is new and empty or already has content. This way, already filled-in data is never lost by applying a template. Enabling the toggle means You are deliberately choosing to let already filled-in fields be replaced by the values from the template - more on this in the next section.
What does "Overwrite values" mean?
The Overwrite values toggle specifically controls the behavior of flavors and flavor groups:
When enabled, flavor values from the template are also applied, and flavor groups that don't exist in the template are removed. Flavors from removed groups are moved into the first remaining group.
If the toggle is enabled, You are actively choosing to let already filled-in flavor values be replaced by the values from the template - including the structure of the flavor groups. If the toggle is disabled, existing values and structures are preserved and supplemented with the template's data.
Watchers from project roles in templates
In addition to individual people or teams, You can also assign a project role as a watcher within a task template - at the same place where You would otherwise add people to watch a task (🔔 icon > Add watcher).
When the template is applied - whether by creating a new task or by applying it to an existing task - all people currently assigned to that project role in the target project are automatically added as watchers.
- If the project role stored in the template doesn't exist in the target project, it is simply skipped when applying the template - no error occurs.
- Applying a template only ever adds watchers, never removes or replaces them - regardless of the state of the
Overwrite valuestoggle.
Note: Project roles are an Enterprise feature. Learn more in the article Project Roles.
Applying templates to existing subtasks
Templates can also be applied to subtasks. However, if a template itself contains subtasks, those are ignored when the template is applied to a subtask.
Comments
0 comments
Please sign in to leave a comment.