How to make a Jira Epic template with sub-tasks

Jira Cloud · updated 3 November 2026 · by AurumFlux, an Atlassian Marketplace Partner

The question comes up every few weeks on the Atlassian Community: a team ships the same shape of work again and again (a release, a feature rollout, a client onboarding), and every time someone retypes the same Epic, the same eight tasks, the same sub-tasks under them. Something gets forgotten, and the board drifts. Here are the three ways to stop retyping it in Jira Cloud, with what each one carries and what it leaves out.

1. Clone an existing Epic

Open an Epic that already has the right children, click ••• → Clone. Jira copies the issue itself; the clone dialog also offers to copy sub-tasks of the issue you are cloning. Child issues that sit under an Epic as separate work items (tasks, stories) are their own issues, so check what the dialog offers on your site before relying on it.

Carries: summary, description, most fields of the cloned issue, and sub-tasks when the box is ticked.
Leaves out: anything that should change per copy. Version numbers, dates and owner names stay as they were in the original, so each clone is a round of hand edits. The original Epic also has to stay alive as the "golden" copy, and the first person to work in it by mistake breaks the mould.

2. An Automation rule

Project settings → Automation. A rule with the trigger Work item created, a condition on the issue type (or a label), and a chain of Create work item actions can build the children automatically. Smart values such as {{issue.summary}} carry text from the trigger issue into the new ones.

Carries: a fixed tree, built with no clicks at all, every time an Epic is created that matches the condition.
Leaves out: choice. The rule fires on every matching Epic whether or not you wanted the tree. One rule is one shape; a team with four kinds of Epic needs four rules, or a label scheme to pick between them, and only a project or site admin can edit any of it. Rule runs also count against the site's monthly Automation limit.

3. A template you apply from the Epic's ••• menu

This is what our app does. You write the tree once as a template, and anyone on the project adds it under an Epic (or a task) when they choose to, filling in the parts that change.

Write the template once

Install Issue Templates by AurumFlux from the Atlassian Marketplace (free for teams of up to 10 users, paid above that). Then open Apps → Issue Templates and create a template. The children are one issue per line, two spaces of indent per level, with {{variables}} wherever the text changes per copy:

Task: Cut release branch {{version}}
  Sub-task: Freeze main and tag {{version}}
  Sub-task: Run migration dry-run
Task: Verify {{version}} on staging
  Sub-task: Smoke-test the checkout path
Task: Ship {{version}} to production

Root issue type Epic; variables version. Scope it to one project, or make it global.

Apply it from any Epic

  1. Open the Epic. Click ••• (More actions) → Apply template.
  2. Pick the template and type the variable values, e.g. version=2.1.
  3. Click Apply. The three tasks and three sub-tasks are created under that Epic, with 2.1 filled in everywhere.

What happens when the project does not match

Before anything is created, the app reads the project's current issue types and create-screen fields. If the template names a type the project does not have, puts a child at the wrong level, is applied to the wrong kind of issue (an Epic template on a Task), or needs a field the project requires and the template does not fill, the apply is refused and it says what does not match. Nothing is created. If Jira still refuses a create part-way (a workflow validator, say), the issues that apply already made are deleted again, children first, and the result lists them. Applying twice does not build the tree twice.

CloneAutomation ruleTemplate (this app)
Who can set it upAnyoneProject/site adminAnyone the admin allows
Per-copy values (version, date)Edit by hand afterSmart values from the trigger issueAsked for at apply time
When it runsOn clickOn every matching createOn click, from the issue
Several shapes of EpicOne golden copy eachOne rule eachOne template each, in a library
Checks the project firstNoNo; a broken rule fails mid-runYes; refuses before creating
Honest limits of the app today: Jira Cloud only; templates carry issue type, summary and description (not attachments, links or custom-field values); trees up to four levels; no apply from inside Jira's global create dialog. The full field reference is on the documentation page.

Which one should you use?

Clone, if it is one Epic a quarter and the children barely change. An Automation rule, if every Epic of a type must get the same tree with no human in the loop. A template, if people need to pick the tree at the moment they create the work, fill in what changes, and trust that a project change will stop the apply instead of leaving half a tree behind.

AurumFlux is an Atlassian Marketplace Partner. Atlassian and Jira are trademarks of Atlassian Pty Ltd; this app is made by AurumFlux and is not made or endorsed by Atlassian. Questions: hello@aurumflux.co.