Epic Clone Cloud Documentation
Breadcrumbs

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.

Overview

Epic Clone enhances Jira's cloning capabilities by allowing you to clone entire work item hierarchies, including parent and nested child items, across different spaces.

Key Features

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

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

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

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

  • Clone in Background: Initiate the cloning process and proceed to your next task, allowing the cloning to occur seamlessly in the background.

  • Cloning API: Further automate your workflows by triggering the cloning from external systems or by Jira Automation rules

  • Bulk Clone from Item Navigator: Search for items in the item navigator and clone them together in a single bulk operation.

Usage Instructions

Work Item View

  1. Accessing Epic Clone: After installing the app, find the "Clone Work Tree" option in the item actions menu (three dots in the top right corner).

    image-20250417-064402.png
  2. Configuration: Select the clone option to open the clone configuration screen. For detailed configuration, refer to this guide.

Item Navigator

  1. Accessing Bulk Clone: After installing the app, find the "Bulk Clone" option in the Apps dropdown right on top of the item navigator.

    image-20251123-070639.png
  2. Configuration: Select the bulk clone option to open the clone configuration screen. For detailed configuration, refer to this guide.

Use Cases

  • Template Projects: Establish template items within a designated project and duplicate them into active projects as needed.

  • Recurring Modules: Quickly set up project structures by cloning template epics with associated child items.

  • Ensure Quality: Effortlessly recreate established structures without the need to generate work items from scratch repeatedly. This approach guarantees that no crucial details are overlooked.

Want to know more? Find additional use cases here:

Access Settings

  • Jira Administrators: Control app accessibility by restricting it to specific projects or user groups. Limit usage to internal users if necessary.

  • Attachment Cloning: Define for each individual project if it should be allowed to clone attachments from the project or not.

  • REST API Access: Jira administrators have the ability to determine whether all users can access the cloning API or if this feature is restricted to administrators only.

Read more about the app settings for Jira administrators in this guide.

Support and Feedback

If you experience a bug or have suggestions, visit our service management portal or contact us via support@ij-solutions.atlassian.net.