The complete Jira template library
Two shapes of reusability, one library. Generate entire task trees from a paste-tree template, or fill any description with a preset. Copy-ready, with hierarchies, roles, priorities, and date offsets.
No credit card required · Starts inside Jira
Preview every template — no signup. Paste, run Smart Replace, review the detected markers, and create the full task tree in Jira in one batch. See the full workflow.
Task Templates
Generate 18–187 linked issues with hierarchy, assignees, sequenced dates.
Description Presets
Drop-in markdown bodies for user stories, bug reports, ADRs, PRDs, postmortems.
Browsing, not reading? Jump straight to the library.
Task templates or description presets?
The library holds two different things and the difference decides which half you want. Both are copy-ready text. Only one of them creates issues.
Task templates — a whole issue tree
One epic, its tasks, their subtasks, with a type, an owner, a priority and a date on every row. SOC 2 Type II Audit Prep is 187 issues: 1 epic, 32 tasks, 154 subtasks, nine named roles, and a due date on every row but the epic. Paste it and the whole programme exists in Jira. 21 of these, across seven team categories, 1,049 issues between them.
Description presets — the body of one issue
User story, bug report, ADR, postmortem, definition of done. Headings, acceptance criteria, and the questions a ticket has to answer before anyone can pick it up. A preset never creates an issue — it fills one that already exists, or every row in a batch at once. 17 of these, across six formats.
Asking what work there is? You want a task template. Asking what this one ticket has to say? You want a preset. Most teams end up with both — apply a preset inside a task template and every issue in the tree lands with a written-out description instead of a bare title.
What a Jira issue template is — and what it isn't
You can already produce issues in bulk three other ways. Here is where the line falls.
It isn't a cloned issue
Clone copies one issue and whatever had gone stale in its fields. A template carries the shape of the work: hierarchy, an owner per row, and dates written as offsets rather than fixed days — so applying it in November produces the same schedule it produced in March.
It isn't an automation rule
A rule fires on an event, and someone has to own it, change it and remember it exists. A template is text you paste when you decide to, in any project where you can create issues. Nothing runs in the background.
It isn't a CSV import
CSV moves rows. You still maintain the column mapping and the parent-child links yourself, and the file says nothing about what the rows should be. The value here is the thinking in the tree — moving it is the easy part.
What makes a template survive contact with a real team
Most published Jira templates are a list of task titles. Four properties separate one you apply from one you rewrite.
- Roles, not names.
@release_lead, not@jane.smith. Smart Replace matches a real handle to a Jira member; a role with no match stays unresolved so you can promote it to a variable. Promote it once and it covers every row that used it —@release_leadon 27 lines becomes one picker when the template is applied. - Offsets, not dates.
[Due + 5d]and[Due + 5bd]resolve against an anchor date you pick at apply time, and business-day offsets skip weekends. Saved as a template, a date variable can also step over public holidays for a region and your own company days off — how a date variable resolves. - Four fields, not forty. Every template here sets exactly four things per row: issue type, assignee, priority, date. Story points, sprints, components and fix versions stay empty on purpose — they belong to the team applying the template, and pre-filling them turns a 40-issue import into 40 edits.
- A review step before anything is created. Smart Replace shows you every match it made — types, people, priorities, dates — while the issues are still text. A template you can't inspect first is one you won't trust twice.
When a template isn't the answer
A template you have to fight is slower than typing. Four cases where the honest advice is to do something else:
- Under ten issues you already know by heart. Finding the right template costs more than writing them.
- Discovery work whose shape you don't have yet. A template asserts an answer. That is the wrong move before you have one.
- Approvals, gates and status transitions. Those live in a Jira workflow, not in a task tree.
- A document that already has structure — but not this one. A spec, a transcript or a page of notes is an extraction problem, not a template problem.
Start with the library below — every template previews in full, with no signup. If your source material is a document rather than a process, bulk-creating Jira issues from text is the faster path. And once a tree you pasted is worth keeping, Jira issue templates with variables covers what it can do as a saved template.
How to import
Two shapes, two ways to bring a template into Jira
Pick the right doc for the kind of template you copied — every step shown with real screenshots.
Paste an outline, get a typed Jira tree
Paste any task tree with markers like [#task], @assignee, !High, [Due + 5d]. Smart Replace matches each token to live Jira data and creates the whole hierarchy in one batch.
Apply a structured body to any issue
Pick a preset (user story, bug report, ADR, postmortem), fill the variable pills it exposes, and the markdown body drops into the description field — for the current issue or every row in a batch. Inside a template, presets also reuse the template's own variables automatically.
Every template page, in one index
Each of these has a page of its own: the full structure it creates, who it's for, and how to import it. The shorter description formats are collected on the description presets hub instead, and every template in the library above previews in full without leaving this page.
Can't find what you need?
Every template is customizable. Save your own task trees and description presets with variables — reuse them across projects and share with your team.