Blog ·
Jira user story template: copy it, set it as a default, reuse it
A Jira user story template is a fixed outline for the Story work item: a one-line statement in the form "As a [user], I want [goal] so that [reason]", followed by acceptance criteria and a few short sections your team fills in the same way every time. Jira Cloud does not hand you one. You paste the outline into the Description, and then decide how Jira should offer it: as a default description, through an Automation rule that adds it on creation, by cloning a model story, or with an app. This guide gives you a template you can copy now, then each way to make it stick, and ends with the small group of stories that should not be typed at all because they come back on a schedule.
Everything said here about Jira's own behaviour is as of October 2026, from Atlassian's documentation and support articles.
The template, ready to paste #
Copy this into the Description of a Story and replace the brackets. It works in team-managed and company-managed projects alike, because it is only text.
As a [type of user], I want [an action or capability] so that [the benefit].
Acceptance criteria
1. Given [a starting situation], when [the user does something], then [what they see].
2. Given ..., when ..., then ...
Out of scope
- [What this story deliberately does not do]
Notes and links
- Design: [URL of the mockup]
- Related: [work item keys]
Definition of done
- Acceptance criteria pass
- Reviewed and merged
- Product owner has seen it
That is the whole template. The rest of this guide is about the parts people get wrong, and about getting Jira to put it in front of the next person who clicks Create.
What each part of a user story is for #
Atlassian's own agile guide describes the statement as a three-part sentence:
"As a [persona], I [want to], [so that]." Source: Atlassian, User stories with examples and a template, read October 2026
The same guide adds the reason acceptance criteria belong in the template rather than in someone's head: "Including acceptance criteria helps teams understand what success looks like and ensures that the story is testable."
| Part | What it answers | Common mistake |
|---|---|---|
| As a [user] | Who this is for | Writing a job title when the behaviour is what matters ("As a user") |
| I want [goal] | What they are trying to do | Describing the solution ("I want a dropdown") |
| So that [reason] | Why it matters | Leaving it out, so nobody can judge a trade-off later |
| Acceptance criteria | When the story is done | Vague lines that cannot fail ("works well on mobile") |
| Out of scope | What it is not | Skipped, then argued about in review |
| Notes and links | Where the context lives | Pasting a whole spec instead of linking to it |
| Definition of done | The team's shared finish line | Repeating it differently on every story |
Atlassian's guide also names the "3 C's": the Card (the written story), the Conversation that clarifies it, and the Confirmation, which is the acceptance criteria. A template can only hold the first and the third. It is a starting point for the conversation, never a replacement for it.
Writing acceptance criteria that can fail #
The Given / When / Then shape in the template is optional, and it earns its place because each line becomes a check someone can run. "Given I am signed out, when I open the invoice link, then I am asked to sign in" either happens or it does not. "Login should be secure" cannot fail, so it cannot pass either. Three to six criteria is a healthy range for a story that fits in a sprint; more than that usually means the story wants splitting.
A filled-in example #
As a returning customer, I want to reorder a past purchase from my order history so that I do not have to search for the same items again.
Acceptance criteria
1. Given I have a past order, when I open Order history, then each order shows a Reorder button.
2. Given an item is out of stock, when I press Reorder, then the other items go to my cart and I see which one was skipped.
3. Given I am signed out, when I open Order history, then I am asked to sign in first.
Out of scope
- Editing quantities before reordering
Four ways to make Jira start every story from it #
Pasting by hand works until the third person forgets. These are the ways to have Jira supply the outline instead, from the lightest to the most structured.
| Option | Where it applies | When the text appears | What it costs you |
|---|---|---|---|
| Default description on the work type | Team-managed projects | On the Create screen, before anyone types | Nothing, it is built in |
| Custom field plus workflow post functions | Company-managed projects | On the Create screen | A field, a screen change and two post functions to maintain |
| Automation rule on Work item created | Either | After the story is created | Rule runs count against your Automation usage |
| Clone a model story, or a template app | Either | When someone chooses to apply it | Manual each time, or an app to install |
Option 1: A default description in a team-managed project #
If your project is team-managed, this is the answer and you can stop here. Atlassian's support article on default descriptions puts it plainly: "You can set a default description template for new issues in team-managed projects." You set it on the Story work type's Description field in the project settings, and every new story opens with the outline already in place.
Option 2: The custom-field route in a company-managed project #
The same article continues: "this feature isn't available in company-managed projects." Its documented workaround is a paragraph custom field (their example name is TemplateDescription) that holds the template as its default value and appears only on the Create screen. Two post functions on the Create transition then copy it into the real Description and clear the custom field. The Description field itself comes off the Create screen so nobody types into the wrong box.
It works, and it is the most invisible option for the person creating the story. The cost is upkeep: a separate Create screen, a field context, and a workflow change that every future workflow edit has to preserve. If your Jira admin is not the person asking for the template, agree on this one with them first.
Option 3: An Automation rule that adds the outline on creation #
Atlassian's Automation knowledge base describes a rule for exactly this: trigger Work item created, a condition that the work type equals Story, and an Edit work item action that sets the Description. Their example keeps whatever the creator already typed and appends the template underneath it, using the smart value {{issue.description}} on the first line. Replace the description outright if you would rather the template win.
Two things to know before choosing it. The template arrives after the story exists, so the person creating it never sees the outline while they write. And each run of the rule counts toward your site's Automation usage, which is worth a look on a busy backlog; our Jira Automation pricing breakdown covers how that usage is counted.
Option 4: Clone a model story, or use a template app #
Many teams keep one well-written story called "TEMPLATE: user story" and clone it. That is free and needs no admin, and it relies on everyone remembering where the model lives and editing out the clone prefix. Template apps such as Issue Templates for Jira and Easy Templates for Jira store the structure properly and apply it on demand, which matters more for epics with child stories than for a single story outline. Our Jira task template and Jira epic template guides compare those routes in more depth.
When the manual way is enough #
Most user stories are unique. They come out of a refinement session, someone writes them once, and they are never repeated. For that work:
- A default description (Option 1 or 2) is all the template you need. It nudges the format without anyone thinking about it.
- A pasted outline is fine for a small team that refines stories together, because the conversation catches what the template misses.
- Do not automate the writing. A generated story with no real "so that" is worse than no story, because it looks finished.
User stories that come back every sprint #
A minority of stories are the same every time: the dependency upgrade the team does each sprint, a monthly accessibility pass, the quarterly review of feature flags nobody has removed, a release-notes story before each release. Their statement and acceptance criteria do not change; only the date does. For those, a template still leaves somebody remembering to create the story, and that is the step that slips.
Recurring Work Items for Jira handles that group. A rule stores the work type (Story, if that is what your team uses), the summary, the description with its acceptance criteria, labels, priority, assignee and an ordered list of subtasks, and creates the story on the pattern you pick: daily, weekly, on a day of the month or the nth weekday of the month. Text fields take tokens, so a summary such as Dependency upgrades {{now.monthName}} {{now.year}} reads as a date in the backlog; the tokens page lists them. The editor shows the next run dates before you save, and every story a rule creates carries a label naming the rule, so finding every past instance is one search.
One honest limit: the app writes the description as plain text. Blank lines become paragraphs and line breaks are kept, so the template above arrives readable, but it will not turn the list items into Jira's bulleted list formatting. If your team relies on headings and checklists inside the description, a template app is the better fit for those stories.
It is also deliberately scoped to the project you turn it on in, so one team's recurring stories never land on another team's board. For the wider picture of repeating work, see Jira recurring tasks, and for where these stories fit in your sprint, Jira sprint planning.
Frequently asked #
Does Jira have a built-in user story template? #
Not as a saved template you pick from a list. Team-managed projects can set a default description on the Story work type; company-managed projects need the custom-field workaround, an Automation rule, or an app.
Should acceptance criteria go in the description or a custom field? #
Either works. The description keeps everything in one place and needs no admin. A dedicated field makes the criteria searchable and reportable, at the cost of one more field to configure. Start in the description and move only if you find yourself searching for them.
How long should a user story be? #
Short enough to read in a minute. One statement, a handful of criteria, and links to anything longer. If it needs a page of explanation, it is probably an epic.