Templates

Creating a template

Build a reusable tree in the visual builder, or capture existing work with Save as Template — with a full reference to the fields each kind of node can carry.

There are two ways to start a template: build it from nothing, or capture work you've already shaped. Capturing is usually faster.

Option A — capture existing work

If the structure already exists somewhere in your map, freeze it:

Right-click the workstream or item you want to capture — on the map, in the items table, or from the workstream column's menu.
Choose Save as Template…
Give it a Template name (up to 100 characters).
Click Save & open builder.

The whole subtree comes across — everything nested beneath it, sub-items included.

What gets captured, and what doesn't

Copied: titles, descriptions, work types, dates, assignees, teams, priorities, tags, estimates, and custom-field values.

Not copied: calculated and Service Desk fields, statuses, boards, comments, attachments, and relationships.

Every value arrives as a fixed value. Open the builder afterwards to turn any of them into a question.

The new template is saved Private — only you and lands on your Templates page.

Option B — build from scratch

Open Templates in the sidebar and click New Template.
Give the template a Template name and an optional Description.
Click Add root and pick what the template starts with — a Workstream, or a work item of a particular type.
Keep building with the row controls: Add child, Duplicate node, and Remove node. Drag the handle to reorder.
Select any node to edit its fields in the Node panel on the right.
Click Save Template.

A template starts with either workstreams or work items of one work type — never a mix. The builder enforces this quietly: once you add the first root, the add menu narrows to only what's legal alongside it.

This is what determines the Applies to chips in the header, and therefore where the template can be applied later. See placement rules.

Child types follow your hierarchy

Inside the tree, a work item must be a direct child type of its parent, according to your organization's work-type hierarchy. The Add child menu only ever offers legal types, so you can't build an invalid tree by accident. If nothing is legal beneath a node, the menu says Nothing can be added here.

Work items can also carry sub-items, which are always leaves.

Reading the structure three ways

The Structure pane offers up to three views of the same tree:

View	Shows
Tree	The shape — hierarchy, nesting, order
Fields	A wide table of every configured value at once, with Title pinned
Timeline	Day offsets drawn as bars against a chosen date variable

Timeline only appears once at least one date in the tree is derived from a date variable — until then there are no offsets to draw. If you remove the last such binding, the view falls back to Tree.

The Fields view is the fastest way to audit a template before sharing it: every node's description, dates, assignee, team, board, priority, labels, points, estimates, and custom fields in one table. Empty cells show —.

What each kind of node can carry

Workstream node

Title, Description (rich text), Start date, Due date, and Colour.

Work item node

In the order the Node panel shows them:

Field	Notes
Title	Required. Accepts `{{tokens}}`
Description	Rich text. Accepts `{{tokens}}`
Start date / Due date	Fixed, or derived from a date variable with a day offset
Team	Fixed or variable
Assignee	Fixed or variable. Constrained by the node's team when one is set
Board	None, Fixed, Variable, or Cycle — see below
Priority
Tags	Only when the work type has labels configured
Point effort	Only when the work type enables points
Time estimate	Only when the work type enables time estimates
Custom fields	Grouped under a Custom fields heading, with a "N of M set" tally

An assignee outside the team is dropped

If a node sets both a team and an assignee, the assignee must be on that team. Someone outside it is silently dropped when the item is created, so the builder warns you and clears the value rather than letting you save something that won't take effect.

Sub-item node

Title, Description, Start date, Due date, and Assignee. A sub-item never carries its own team — it inherits the parent item's, and the panel says so.

Board placement

The Board row offers four modes:

Mode	What happens on apply
None	The item is created without being placed on a board
Fixed	Always the one board you pick now
Variable	Whoever applies the template picks the board or cycle
Cycle	Resolved against a cycle-enabled board folder at apply time

Cycle is the useful one for recurring work. Instead of pinning to a specific board, you pick the board folder and an offset relative to whatever cycle is current when the template is applied — Current Cycle, Current Cycle +1, Current Cycle -1, and so on across a range of past and future cycles. A template that always drops work into next sprint keeps doing so months later.

Saving

Save Template commits your changes. Some limits are only checked at save, so you may see a validation message from the server in a red banner at that point:

At most 500 nodes (workstreams, work items, and sub-items combined)
At most 10 levels deep — sub-items don't count as a level
At most 20 variables
Titles up to 500 characters once resolved

Nothing is saved until you press Save Template, including turning the Variables toggle on or off.

Variables — make fields ask a question
Applying a template — preview and create the work

Overview

Templates capture a reusable tree of workstreams, work items, and sub-items so you can stamp out the same shape of work again and again — with the right owners, dates, and fields already in place.

Variables

Turn a fixed field into a question the template asks when it's applied — the eight variable types, token interpolation in titles and descriptions, and dates derived by day offsets.