Project templates
Stop configuring the same statuses, task types and labels for every new project.
Once you have set up a project the way your team works, save it as a template and the next one starts there.
What a template holds
- Statuses and the workflow between them
- Task types
- Priorities
- Labels
- Feature toggles for the project
Templates carry taxonomy, not work. No starter backlog, no pre-made tasks. Every team we looked at edited a starter backlog into something unrecognisable before touching it, which makes it a chore disguised as a head start.
Creating one
From an existing project: Project → Settings → Save as template.
Or from scratch: Settings → Templates → New template.
Using one
Pick the template when creating a project. You see exactly what it will create — the statuses with their colours, the task types, the labels — before you commit. A template you cannot inspect before applying is one nobody trusts twice.
Applying to an existing project
You can apply a template to a project that already exists. This is strictly additive: it adds statuses, types and labels that are missing and never removes or renames anything.
You get a preview of exactly what will be added first.
Additive-only is not a limitation we mean to lift. Removing a status that tasks are sitting in would have to either delete those tasks or leave them in an invalid state, and neither is something to do as a side effect of applying a template.
Managing templates
Settings → Templates — rename, duplicate and delete. Duplicating is the way to make a variant: "Client project" and "Client project (retainer)" sharing most of their taxonomy.
Editing a template does not change projects already created from it. A template is a starting point, not a live link.