Epic Clone

What does epic Clone do?

With Epic Clone, you gain the added feature of cloning an issue along with all its child issues. Unlike the standard clone function in Jira, which only allows you to clone the issue with optional attachments, links, or sub-tasks, 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 customization extends to cloning into a different project and transitioning between company-managed and team-managed projects. The following attributes of the issue can be modified:

How can Epic Clone be used?

Upon installing the app, you will notice an extra option in the issue actions menu (located as three dots in the top right corner) labeled as "Clone with child issues".

Open

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 application could be of great interest to you, especially if you encounter recurring template challenges. Its cross-project clone feature enables you to establish template issues within a designated project and duplicate them into active projects as needed.

Consider a scenario where you work at a software development firm and require certain modules in every software project you undertake.

These modules may 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 to your new project in a single step for each epic. This streamlined process not only saves you considerable time compared to manually setting up a new project 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