Page Comparison

What does epic Clone do?

With Epic Clone, you get the additional functionality to clone gain the added feature of cloning an issue together along with all its child issues. The Unlike the standard clone functionality function in Jira, which only lets allows you to clone the issue with (optionally) optional attachments, links, or sub-tasks. For epics as an example, issues which are linked to the epic by the epic link or parent field can't be cloned together with the epic within the same clone process.Epic Clone furthermore provides the possibility to configure , Epic Clone enables you to clone items, their child issues and linked issues within a single cloning process.

Moreover, Epic Clone offers the flexibility to customize the cloned issues. This includes also the customization extends to cloning into a different project . Cloning from and transitioning between company-managed - to and team-managed - projects and vice versa is also possible. The following attributes of the issue attributes can be changedmodified:

How can Epic Clone be used?

After installation of Upon installing the app, you will see notice an additional entry extra option in the issue actions menu (located as three dots in the top right corner) . It is called labeled as "Clone Templatewith child issues".

Image Removed

Image Added

If you click on that entry, the clone configuration will open.

Details about the clone configuration are explained here: Clone Configuration When you select the clone option, it will trigger the opening of the clone configuration.

For a comprehensive understanding of the clone configuration, refer to the following details: Where to find Epic Clone?

What can Epic Clone be used for?

The app might be interesting for you application could be of great interest to you, especially if you have template issues you want to reuse. The encounter recurring template challenges. Its cross-project clone functionality allows to set up feature enables you to establish template issues in within a template designated project and copy duplicate them to productive projects whenever it is necessary.Imagine you are working in into active projects as needed.

Consider a scenario where you work at a software development company firm and have some require certain modules you need in every single software project you writeundertake.

For those These 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 entail similar stories across various projects. Having them stored in a template epic would significantly reduce the time and effort required for issue creation and structuring. By simply cloning the template epic along with all its associated issues when needed, you can swiftly establish the project structure at the project's outset.

By utilizing Epic Clone, you can effortlessly replicate the template epics and issues easily to your new project in one action a single step for each epic. Compared to the manual setup of This streamlined process not only saves you considerable time compared to manually setting up a new project this will save you a lot of time and you can focus on the really important topics!but also allows you to concentrate on the core aspects of your project.

Access settings for Jira administrators

Jira administrators have the ability to control the accessibility of Epic Clone, restricting it to specific projects or user groups. For example, if you prefer the app to only function in template projects, you can confine Epic Clone to those particular projects. Users will then be restricted from utilizing the app in any other projects apart from the ones specified in the app settings.

Moreover, you may opt to limit the app's usage to internal users exclusively, thereby preventing external users within your instance from accessing it. This restriction can be easily implemented by choosing only groups containing internal users within the app settings.

For more comprehensive information regarding the app settings, please refer to the documentation. App settings