How to clone existing Epic tasks/subtasks to new Epic (Automation)

[Nicolas Shinozaki]

The goal is to be able to have an existing Epic template such that all new Epics created inherit its tasks/subtasks. Given that Epic Link has been deprecated, how would you go about doing so. 

[Peter_DevSamurai]

Hi @Nicolas Shinozaki , 

This is is a little complicated so bear with me :) When a new Epic is created, automatically clone tasks/subtasks from your template Epic ->  Link them using the Parent field. No nested branches needed, but it requires 2 interconnected rules (1 for tasks, 1 for subtasks) and a temp hack to track originals (appending keys to summaries).

A. Prerequisites (Must-have set before you get started)

• Update Automation for Jira (Data Center compatible)
• Create a template Epic (ex: key TEMP-1) with your standard tasks/subtasks. Use the Parent field for links (Settings > Issues > Issue features > Enable parent-child relationships if not already).
• Test in a sandbox project as clones won't copy history/comments/attachments (add those actions if needed).

B. Rule 1: Clone Tasks from Template to New Epic

• Scope: Global rule (Project automation > Create rule).
• Trigger: Issue created.
• Condition: Issue type equals Epic (to fire only on new Epics).
• Action 1: Lookup issues – JQL: parent = TEMP-1 AND issuetype = Task (replace TEMP-1 with your template key; use Epic Link = TEMP-1 if Parent isn't fully rolled out).
• Branch: For: issues found (from lookup).
  • Action in Branch: Create issue (clone mode) – Project: Same as trigger | Issue type: Same as original | Summary: {{issue.summary}} (from {{issue.key}}) (appends original key for subtasks rule).
  • Action in Branch: Edit issue – Fields to set: Parent = {{triggerIssue.key}} (links to new Epic).
• Rule Details: Check "Allow rule trigger" (enables Rule 2 below).

You can refer to this article: Clone Stories linked to Epic

C. Rule 2: Clone Subtasks Under Cloned Tasks

• Scope: Global rule.
• Trigger: Issue created.
• Condition 1: Issue type equals Task (or your story type).
• Condition 2: Issue summary contains "from" (to catch appended keys; use a custom text field like "Original Key" for cleaner tracking if preferred).
• Action 1: Create variable (if supported in your AFJ version; else use Edit issue to set a temp field): originalKey = {{issue.summary.match("from (.*?)")}} (extracts key via regex smart value).
• Action 2: Edit issue – Summary: {{issue.summary.replace("( from .*?)$","")}} (cleans up appended key).
• Action 3: Lookup issues – JQL: parent = {{originalKey}} AND issuetype = Sub-task.
• Branch: For: issues found (from lookup).
  • Action in Branch: Create issue (clone) – Parent: {{triggerIssue.key}} | Other fields as needed.
• Rule Details: No "Allow rule trigger" needed.

This creates the full hierarchy under your new Epic instantly. For subtasks of subtasks (rare), add a third rule. If regex feels brittle, use a custom link type ("Clones via rule") to track originals instead of summary hacks.

If this won't work out, you can opt to using Marketplace apps like Deep Clone for Jira or Epic Clone. 

You can also upvote this feature request for native templates for future :)

Best, 

Peter

[John Funk]

Hi Nicolas - Welcome to the Atlassian Community!

I would create an automation rule based on a work item created trigger. Then add a condition for issue type = Epic and add any other conditions that identify that specific Epic to have the children created. 

Then add actions to create work item (as many work items as you want to have created under there). If you want some fields to be populated with values from the Epic, then select those fields, click the 3 dots next to the field box and select Copy. Then click on the result and change Current work item to Trigger work item. 

Also include the Parent field and populate with the Trigger issue. 

Then you should be good to go. 

[Clara Belin-Brosseau_Elements]

Hi @Nicolas Shinozaki

If you’re looking for a faster and more straightforward solution compared to Automation to clone an Epic with all its subtasks, I can suggest trying our app Elements Copy & Sync.

In the app, go to Recipes → Create recipe:

1. Scope:

• Choose Epic as the Source issue type.

• Optionally restrict it to a specific project or JQL filter if you only want certain Epics to be cloned.

2. Content tab:

• Enable Copy full hierarchy → this ensures all child issues (Stories, Tasks, Bugs, etc.) under the Epic are included in the copy.

• Then scroll down and check Copy subtasks → this makes sure that each cloned child issue brings along its own subtasks.

With these two options enabled, running the recipe on an Epic will clone the Epic, its linked child issues, and all their subtasks, keeping the full structure intact.

This solution should be easier to implement than Automation rules. Don't hesitate to try app for free (and it stays free under 10 users).