Eriksen Labs Support

Jira epic template

The outcome, the problem behind it, what is in and out, and how you will know it worked. The page people come back to when the stories start to drift.

Free to copy Standard team style

The template

Change it in the generator

Epic

[Outcome] for [who]

Priority
Jira’s default
Labels
None

Description

Goal

[The outcome in one or two sentences. What is different for users when this is done?]

Problem

[What is wrong today, and why it matters now.]

Scope

  • In: [what is included]
  • Out: [what is not]

How we will know it worked

[A measure, and the number to reach if there is one.]

Before closing

  • All child issues done or moved out
  • Success measure checked
Show it as Markdown
### Goal

[The outcome in one or two sentences. What is different for users when this is done?]

### Problem

[What is wrong today, and why it matters now.]

### Scope

- In: [what is included]
- Out: [what is not]

### How we will know it worked

[A measure, and the number to reach if there is one.]

### Before closing

- [ ] All child issues done or moved out
- [ ] Success measure checked

What a good Jira epic template contains

The goal as an outcome, in one or two sentences. The problem behind it, and why now. What is in scope and, just as important, what is out. How you will know it worked. And a short checklist before the epic is closed. Longer epics add rough milestones and the risks that could hold them up.

The epic holds the why. The stories and tasks under it hold the what, so the epic description stays short enough to reread when a decision has to be made.

When to use it

Use it for a body of work that takes several sprints and splits into stories. The epic holds the why; the stories hold the what.

Keep it short. An epic description that runs to pages is a specification, and belongs in a linked document.

What each section is for

Goal
Written as an outcome, not as a list of features.
Problem
Why now. It is what decides what can be cut when time runs short.
Scope
The Out line prevents more arguments than the In line.
How we will know it worked
Without a measure, an epic is done when the stories run out.
Milestones Detailed
Rough dates are enough here. Exact ones belong in the plan.
Risks and dependencies Detailed
Listed early enough to do something about them.

Sections marked Detailed are not in the template above. Switch them on in the generator, where you can also edit the text and the checklist.

Jira epic template examples

Four kinds of epic, each with its goal, scope, success measure and the child work items it usually has. The children are where the detail goes; the epic only needs enough to judge them against.

Product feature

Summary
Self-service refunds for support agents
Goal
Support agents can refund an order up to a set amount without asking finance.
Problem
Every refund goes to finance by email, so customers wait and agents chase.
Scope
  • In: full and partial refunds on card payments, up to a limit finance sets; an audit entry for each refund
  • Out: refunds on invoices; changes to the refund policy
How we will know it worked
Refunds under the limit are finished on the day they are asked for. Agree the target with finance before starting.
Child work items
  • Story: Agents see a Refund action on an order
  • Story: Finance sets the refund limit
  • Story: Each refund writes an audit entry
  • Task: Update the support handbook
  • Task: Brief the support team

Release

Summary
Release 5.0 to all customers
Goal
Version 5.0 is live for every customer, with release notes published and support ready for questions.
Problem
The last release slipped because testing and the release notes started after the code freeze.
Scope
  • In: features merged before the code freeze; release notes; a support briefing
  • Out: anything merged after the freeze, which moves to the next release
How we will know it worked
Released on the planned date, with no rollback in the first week.
Child work items
  • Task: Code freeze and release branch
  • Task: Regression testing, with a sub-task for each platform
  • Task: Release notes
  • Task: Support briefing
  • Task: Announcement

Migration

Summary
Move shared files from the old file server to cloud storage
Goal
Every department’s shared files are in the new storage with the right access, and the old server is switched off.
Problem
The old server is out of support, and remote staff can reach it only over the VPN.
Scope
  • In: shared folders for every department; their access groups
  • Out: personal folders, which each person moves; archives, which stay read-only on the old server until it is switched off
How we will know it worked
The old server is switched off on the planned date, and no department has to ask for access it had before.
Child work items
  • Task: List shared folders and their owners
  • Task: Migrate one department, with sub-tasks to copy, check access and get the owner’s sign-off (one task per department)
  • Task: Make the old server read-only
  • Task: Switch off the old server

Customer onboarding

Summary
Onboard a new customer to the platform
Goal
The customer’s team uses the platform for its daily work by the date in the contract.
Problem
Without a fixed plan, onboarding steps depend on who runs them, and some get missed.
Scope
  • In: single sign-on, a data import, two training sessions
  • Out: custom integrations, which are quoted separately
How we will know it worked
The customer’s admin signs off, and the agreed number of people have signed in by the end of the first month.
Child work items
  • Task: Kick-off call and plan
  • Task: Set up single sign-on
  • Task: Import data, with sub-tasks for a test import, the full import and a check of the totals
  • Task: Training sessions
  • Task: Hand over to the account manager

An epic like the last one repeats with the same children each time. Our guide to a Jira epic template with stories and sub-tasks covers how to create them together, with and without an app.

How to make this the starting point in Jira Cloud

Jira Cloud has no issue templates as such. These are the native ways to start new epics from this template, as Atlassian’s own pages describe them, and where each one stops. Our guide to Jira issue templates in Jira Cloud compares them in more detail.

Team-managed projects: a default description for Epic

A team-managed project can give each work type a default description. Atlassian’s recap on JRACLOUD-4812 gives the path: Project settings → Issue types, select Description, and write the default text. Choose Epic and paste the template. It sets the description only, one text per work type, and it cannot contain a table (KB). The stories still have to be created one by one.

Company-managed projects: Atlassian’s workaround

The system Description field cannot have a default here. Atlassian’s workaround gives a custom Paragraph field the template as its default value, shows it on the Create screen instead of Description, and copies it into Description with a post function on the workflow’s Create transition. It changes a custom field, screens and a workflow, so plan it with whoever looks after those.

Cloning a reference epic with its children

Keep one epic that is never closed, with the template in its description and its usual stories and tasks under it. Atlassian’s Clone page says ••• → Clone can include an epic’s child work items, as well as sub-tasks and links. The copy’s summary starts with “Clone”, the children keep the reference epic’s wording, and the reference epic shows up on boards and in searches. Anyone who can edit it can change the template for everyone.

Automation that adds the stories

An Automation rule on Work item created, with a condition on the work type, can write the template into the epic’s description with an Edit work item action (KB). Its Create work item action can add the stories too. Both happen after the epic exists, not in the Create dialog, and each rule run counts toward your Automation usage (usage doc). When a rule creates a parent and then children, Atlassian’s KB on cloning with sub-tasks stores the new parent’s key in a variable first, so later children do not end up under the wrong one.

None of these lets someone pick between epic templates in the Create dialog, such as a release epic and a migration epic, each with its own children. That is what an app adds.

Want this as a template people pick in Jira?

Issue Templates & Create Defaults for Jira gives each project a Templates page. Pick a template there and Jira’s own Create dialog opens with the summary, description with its checklist, labels and priority filled in. From version 2.9.0 a template can also set the assignee to the person using it, a due date a number of days ahead, and components; child work items can also be left unassigned. The person can change anything before creating, under Jira’s usual rules for required fields and permissions. Set a default template for a work type, and the Create dialog names it. The app writes nothing into a form by itself. It can also set custom fields (text, number, date, dropdowns and more), and it runs on Jira Cloud only.

Since version 2.7.0, an epic template can also list its stories and tasks, and sub-tasks under them: once the epic is created, they are created under it in that order. See Jira templates with sub-tasks and the documentation on child work items.

To take a template from this page into the app with its formatting, paste it into an issue’s description, then, as a project or Jira administrator, choose Save as template from the issue’s ••• menu.

Questions

What should a Jira epic description include?

The goal as an outcome, the problem it solves, what is in and out of scope, and how you will know it worked. Milestones and risks help on longer epics. Detailed requirements belong in the stories, or in a linked document.

How big should an epic be?

Big enough to need several stories over more than one sprint, and small enough that its goal fits in one or two sentences. If the goal needs a list, it is probably more than one epic.

Can a Jira epic template create its stories too?

Not in one step in native Jira. You can clone a reference epic with its child work items, or have an Automation rule create the stories after the epic. From version 2.7.0, Issue Templates & Create Defaults for Jira lets a template list the stories, tasks and sub-tasks, and creates them in order under the new epic.

Can I set a default epic description in Jira Cloud?

In a team-managed project, yes, as the Epic work type’s default description. In a company-managed project, not for the system Description field. Atlassian’s workaround uses a custom Paragraph field and a workflow post function.

Or build your own in the Jira issue template generator, and see what Jira Cloud does on its own.