Ticket templates
Templates are reusable tickets, organised by epic, that you can drop into any sprint. If your team runs the same checklist every cycle — a release ritual, onboarding steps, a monthly close — build it once as templates instead of retyping it every time.
Where: Templates in the main menu You need: access to the target project
When to use this, and when not to
| The work | Use |
|---|---|
| A ritual you repeat every cycle | Templates |
| A one-off piece of work | An ordinary ticket |
| A backlog you already have listed | Import |
| Consistent wording across all tickets | Ticket Standards |
Template the ritual, not the work. "Deploy checklist" is a template; "Build the invoicing feature" happens once and is a ticket.
Using templates
- Select the templates you want — listed under their epics, with type, priority and status visible.
- Choose the project and the sprint to apply them to.
- Click Apply. Copies of the selected tickets are created in that sprint.
The originals stay untouched — you are stamping copies, not moving anything. Run the same set into next sprint whenever the ritual comes round again.
What Happens Next
- Copies appear in the chosen sprint as ordinary tickets, and behave like any other from then on.
- Copies are independent. Editing a template later does not update tickets already created from it — those were copies at the moment of Apply.
- Assignees are not set by the template; the new tickets need owners like any others.
Tips
- Write the template once, properly. Its title and description are inherited by every copy, so this is the one place where over-writing pays. A vague template produces vague tickets forever.
- Group by epic so a whole ritual can be selected in one sweep.
- Check the target sprint before applying. The copies land where you pointed them; a ten-ticket ritual in the wrong sprint means ten moves or ten deletes.
- Assign immediately after applying. A freshly stamped checklist with no owners is a checklist nobody does.
- Review templates twice a year. Rituals change, and a template describing last year's release process is worse than none — people follow it.
Troubleshooting / FAQ
Q: I edited a template and existing tickets did not change. Expected — copies are independent from the moment they are created.
Q: The templates applied to the wrong sprint. Delete or bulk-move them with List view, and re-apply to the right one.
Q: Nobody is doing the checklist tickets. They have no assignee. Templates create the work; they do not allocate it.