Duplicate Epic Documentation
Please note that we will end support for Duplicate Epic on 30th of April 2021. If you are interested in an alternative which is also available for Jira Data Center please have a look at Epic Clone App: https://ij-solutions.atlassian.net/wiki/spaces/ECP
With the Duplicate Epic app for Jira server you get the additional functionality to clone an epic together with all issues in that epic. The standard clone functionality in Jira only lets you clone the epic issue with (optionally) attachments, links or sub-tasks. Issues which are linked to the epic by the epic link field can't be cloned together with the epic within the same clone process.
Use Case for Duplicate Epic
The demand for having an Duplicate Epic feature in Jira mostly comes up if a template epic exists with a lot of issues inside, which needs to be reused from time to time. If you would use the standard Jira clone function you need to clone the epic and all the issues separately and then link the cloned issues to the cloned epic manually. It can be imagined that this could become time consuming especially if you have a template epic with a lot of issues inside.
The Duplicate Epic Solution
The Duplicate Epic app provides the possibility to clone a template epic together with all the issues inside in one action with just a few clicks.
After downloading and installing of Duplicate Epic on your Jira instance, an additional menu item will appear in the more menu of issues with epic issue type. This menu item is only visible in epics. In other issue types it won't appear in the more menu.
If you click on that menu item, a screen appears where the summary and epic name of the new epic can be inserted. If your epic has attachments, you can additionally select if the attachments shall be copied to the new epic as well or not. Finally, all issues which are linked to the source issue via the epic link field are listed on the screen. The order of the issues in epic will be kept when you clone the epic so the copied issues appear in the same sequence in the new epic than in the source epic.
If you have entered the epic name and summary for the new epic and selected whether attachments shall be cloned as well or not, you can start the cloning process by clicking on the clone button.
Sub-tasks, which are located either in the source epic itself or in the issues in epic, are automatically cloned as well.
Please note: For epics with a lot of issues inside the cloning might fail due to a timeout reached by the cloning process. If the cloning fails an error message appears on the screen and in the Jira log files.