On these pages you find the documentation for the Epic Clone app for Jira.
What does Epic Clone do?
With Epic Clone 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.
Epic Clone furthermore provides the possibility to configure the cloned epic and issues. This includes also the cloning into a different project. The following issue attributes can be changed:
Target Project (also all issues in epic will be cloned to that project)
Find & Replace Function for Description
Labels (add custom label)
Issues in Epic:
Add Summary Prefix
Add Summary Postfix
Labels (add custom label)
Story Points (for Stories only)
For attachments, sub-tasks and linked issues it can be decided whether they should be cloned or not.
How can Epic Clone be used?
After installation of the app you will notify an additional entry in the "More"-Menu of Epics. It is called "Clone Epic Template".
If you click on that entry, the epic clone configuration will open.
The app might be interesting for you especially if you have template epics you want to reuse. The cross-project clone functionality allows to set up template epics in a template project and copy them to productive projects whenever it is necessary.
Imagine you are working in a software development company and have some modules you need in every single software you write. For those modules the different stories may be similar for every project. It would save you a lot of work for creation and structuring of those issues if you would have them in a template epic which you can easily clone with all issues in one go whenever it is necessary. At the beginning of each project you could create the structure with epics and issues a lot faster. With epic clone you can copy the template epics and issues easily to your new project, assign them to the right persons and set the estimation values all in one action for each epic. Compared to the manual setup of a new project this will save you a lot of time and you can focus on the really important topics!
Can the access to Epic Clone be limited?
Jira administrators can limit the access to epic clone to certain user groups or projects. This might be useful if you have large epics, for instance, which should only be copied if the user know what they are doing. In this case the cloning can be limited to administrators for example.
Another use case would be that you only want to allow cloning from special template projects, but not from productive projects in general. Then you can limit the epic clone functionality to those template projects.