The need: clone an Epic and all stories
As a Project Manager, you follow a very complex process which is laid out in an Epic template with stories, tasks, and sub-tasks. In your day-to-day job, you regularly reuse the same set of issues as templates so that your next work session is initialized exactly as you expect it.
The solution: copy the full hierarchy of your Epic tree
Thanks to Elements Copy & Sync, you have the ability to clone an Epic with all its issues in a single action, to any project on your Jira instance. You can even propagate key changes from your Epic template to your cloned Epics with synchronization so your projects are always up-to-date!
Watch the video tutorial or follow the steps below to get started.
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).
This guide explains how to clone the Epic and its three child issues with one single action.
This recipe copies all the fields from the source issue. This part is optional, you can set up your recipe to copy any field you want from the Epic or its issues. The only required field to copy is "Epic Name", which is mandatory to create a new Epic.
1 - As a Jira administrator, go to the "Elements Copy & Sync Cloud" administration and click on Recipes in the navigation bar.
2 - In the Recipes listing page, select "Escalate ticket" in the Active Recipes list.
3- In the Recipe configuration page, click on the Target tab.
4 - In the "Target issue context" section, set "Same as source issue" in the Issue types option.
5 - Click on the Content tab.
6 - In the "More" section, enable the Copy full Epic tree option.
7- Click on the Save button.
With this very simple configuration, 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. The new cloned issues will be the children of the new copied Epic.