Skip to main content
Skip table of contents

Epic Clone

Welcome to the documentation for the Epic Clone App for Jira Cloud. This guide provides comprehensive information on the app's functionality, usage, and configuration options.

What does Epic Clone do?

With Epic Clone, you gain the added feature of cloning a work item along with all its child items. 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 replicate entire hierarchies, including parent and nested child items.

Key Features

  • Comprehensive Cloning: Clone work items, their children, and linked items in one go.

  • Customizable Cloning: Modify attributes such as target project, summary, assignee, labels, components, fix versions, due date, and original estimate.

  • Cross-Project Cloning: Clone work items into different projects and transition between company-managed and team-managed projects.

  • Flexible Configuration: Decide which attachments, links, and child items to clone.

The following attributes of the work item can be modified:

Parent:

  • Target Project (also all child issues will be cloned to that project)

  • Summary

  • Find and replace in description field

  • Decide whether to clone attachments or not

  • Assignee

  • Labels (select from existing labels or create new labels)

  • Components (for company-managed projects only)

  • Fix Versions (for company-managed projects only)

  • Due date

  • Original Estimate

Linked items - parent:

  • Clone links only or linked work items

  • Separately decide which links / linked work items to clone and which not

  • Decide whether to clone parent link or not (only available on Premium or Enterprise plans)

Child items:

  • Separately decide which work item to clone and which not

  • Decide whether to clone attachments or not

  • Summary

  • Assignee

  • Original Estimate

  • Due date

  • Story Points (for Story type only)

Linked items - children:

  • Clone external links or recreate internal links after cloning (see here for details)

  • Separately decide which links to clone and which not

How can Epic Clone be used?

Upon installing the app, you will notice an extra option in the item actions menu (located as three dots in the top right corner) labeled as "Clone Work Tree".

image-20250417-064402.png

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 items 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 work item 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 child items 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

If you experience a bug in the app, if you have an idea for improvement or if you have another topic you want to talk about, feel free to visit our service management or contact us via support@ij-solutions.atlassian.net


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.