Missed Team ’24? Catch up on announcements here.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

How to clone an Epic with all its issues

:woman_raising_hand: Raise your hand if this sounds like your team: you need to copy Epics and all the issues included in them. :man_lifting_weights: Two hands in the air if you create template Epics with issues, tasks, and subtasks so you can easily fill empty new projects.

Reusing the complex process you’ve organized in Epics with stories, tasks, and sub-tasks is the best way to achieve consistency across your teams.

Clone an Epic.png

🛟 Help is on the way: you don’t have to spend hours cloning each issue under an Epic thanks to help from Elements Copy & Sync. You can even propagate key changes from your Epic templates to your cloned Epics with optional synchronization so your projects are always up-to-date!

How to create an clone an Epic with all its issues at once

In this example, we will copy an Epic (with the key DEV-1) which contains three issues (with the respective keys DEV-2, DEV-3 and DEV-4) and 3 sub-tasks (Dev-5, Dev-6, Dev-7).

Let’s see how to configure your recipe so that you can clone the Epic and its three child issues + 3 sub-tasks with one single action.

Step 1

Create a recipe called "Clone Epic"

Create-Epic-clone-recipe-min.gif

 

Step 2

Go to the Target step and select ”Same as source issue"

Select-target-issue-type-min.gif

 

Step 3

Continue to the Content step, and activate the toggle for “Set and synchronize fields”. Then under the “Fields Mapping options” add the target field "Epic Name", which is mandatory to create a new Epic. You can choose the copy it from the source issue, set a static value, or set a dynamic value based on a field value in the source Epic.

Add-epic-name-min.gif

 

If you want to clone other fields, you can add them one by one, or click on the 3 dots to add all available fields.

Add-target-fields.gif

 

💡 Optional: for each field you can decide if you want to synchronize changes from the original source Epic to the new copy. You can also activate the option to create components in the target project if they don’t exist.

Activate-synchronization-min.gif

 

Also optional: copy comments and attachments from the source Epic.

Copy-comments-attachments-min.gif

 

Under the section “More”, activate the toggle for activate the toggle for “Copy full Epic tree” and for “Copy subtasks”.

Full-epic-copy-subtasks-min.gif

 

Step 4

Save and active the recipe

Save-activate-clone-epic-min.gif

 

Step 5

Open the Epic to clone, and trigger the recipe

Clone-epic-and-issues-min (2).gif

 

:clap: Congratulations, you’ve just automatically cloned an Epic with all its issues at once thanks to Elements Copy & Sync.

When a user triggers the "Clone Epic" recipe from Epic DEV-1, Copy & Sync will clone the Epic to any target project along with the three issues within the Epic and the subtasks. The new cloned issues will be the children of the new copied Epic.

Want to go further?

Learn how to limit which users can trigger this recipe, or clone several full Epic trees at once with bulk copy.

1 comment

Comment

Log in or Sign up to comment
Luca Papaiz
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 28, 2024

These instructions don't seem to be updated and are not working.

The step "Copy full Epic three" doesn't exist anymore and the new "Copy Full hierarchy" doesn't seem to do the task.

Please help

Like Nurse Flow likes this
TAGS
AUG Leaders

Atlassian Community Events