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
Using templates
- Select the templates you want — they are listed under their epics, with their 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 around again.
What makes a good template
- Write it once, properly. The template's title and description are what every copy inherits, so this is the one place where over-writing pays. A vague template produces vague tickets forever.
- Template the ritual, not the work. "Deploy checklist" is a template; "Build the invoicing feature" is not — it happens once.
- Group them by epic so a whole ritual can be selected in one sweep.
Rules and things to watch
- Copies are independent. Editing a template later does not update tickets already created from it — they were copies at the moment of Apply.
- Check the target sprint before applying. The copies land where you pointed them; applying a ten-ticket ritual into the wrong sprint means ten moves or ten deletes.