There are two ways to start a template: build it from nothing, or capture work you've already shaped. Capturing is usually faster.
If the structure already exists somewhere in your map, freeze it:
The whole subtree comes across — everything nested beneath it, sub-items included.
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.
Left out: any value that no longer fits your current settings — an assignee who is no longer a member, a persona that is retired or that the assignee does not hold, an archived team, a tag or priority not in the item type's set, a value in a custom field the type no longer uses or that was deleted, a removed custom-field option, and point effort or time estimates the type has switched off. The save still succeeds. When anything was left out, the dialog says so before it opens the builder. It lists each value, for example Assignee "Jane Doe" (no longer a member) on 3 items, so you know what to put back. Choose Open builder to carry on. Through the API, the response carries the same list.
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.
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.
Inside the tree, a work item must be a direct child type of its parent, according to your organization's work-type hierarchy. When a type may sit under several parent types, it can go under any of them. 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.
In the Tree view, drag a sub-item by its grip to move it up or down within its work item. To put a work item's sub-items in alphabetical order in one click, use Sort A→Z on that work item (it appears when the item has two or more sub-items). The sort reads numbers the way people do, so "Step 2" comes before "Step 10", and untitled sub-items go last. Work created from the template gets its sub-items in this order; work created earlier is not changed.
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 —.
Title, Description (rich text), Start date, Due date, and Colour.
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 |
| Persona | Only when your organization uses personas (job functions such as Tech lead or QA). Pairs with the assignee: a fixed assignee must hold the persona, and a retired persona can't be chosen for new work |
| 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 |
A template captured from imported work often carries the same value on dozens of items, such as one assignee or a board from the old tool. Select any item that has the value and click Clear field from every item under that field (for example Clear assignee from every item). It is offered for Description, Start date, Due date, Team, Assignee, Board, Priority, Tags, Point effort, Time estimate and each custom field, but not for Title. Description and dates are cleared from workstreams too.
A confirmation says how many items it will clear. A custom field stays on items whose item type requires it, and the confirmation says how many keep it. Nothing is saved until you save the template.
Title, Description, Start date, Due date, Assignee, and (when your organization uses personas) Persona. A sub-item never carries its own team — it inherits the parent item's, and the panel says so.
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.
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:
Nothing is saved until you press Save Template, including turning the Variables toggle on or off.
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 nine variable types, token interpolation in titles and descriptions, dates derived by day offsets, and yearly dates.