Epic duplication made effortless

Create Jira epic templates, copy Jira issues to another project, and save time and energy like never before.

Clone entire epics in minutes, not hours

No self-respecting product manager, project manager, or software engineer should have to duplicate issues in Jira one by one to kick off a new project.

Start by creating a Jira epic template

Create a Jira epic template with an approved issue structure (Epic – Issue – Sub-Tasks) that you can effortlessly clone and customize for any need.

Bulk copy Jira issues in 3 easy clicks

Get new projects up and running in the blink of an eye by cloning what you need—including child issues—across projects. Before cloning, modify parent issue fields to ensure consistency.

No coding. No automation. No sweat.

We believe anyone—not just Jira pros—can go beyond the limitations of Jira. Epic Clone works effortlessly as an enhancement to the Jira interface that you know and love, no technical expertise required.

Ready to bulk clone in Jira?

Pick a plan that best suits your needs and get started. Don’t see what you need? Talk to us.

See Epic Clone in action

Get in touch with our team to find out just how effortlessly Epic Clone helps teams save time and energy.

See the difference

Discover why Epic Clone is the smarter choice over Jira’s native cloning—more power, less hassle.

Epic Clone FAQ

Epic Clone is an Atlassian Marketplace app that allows you to clone an epic or any other parent item along with its child issues, sub‑tasks, and optionally linked items—all in one single clone operation. It’s ideal for establishing reusable templates (Epic → Issues → Sub‑Tasks) and quickly replicating them across different projects without manual work

Cloud version: Yes, with Epic Clone you can copy work items of all types. It doesn't have to be an Epic.

DC version: Epic Clone is currently only available in the Epic issue type.

Yes, copying items across projects is possible in both, Cloud and DC version of the app

Yes. Users must have the necessary permissions in the target project to:

  • Create issues
  • Add attachments (if attachments shall be copied)

  • Assign items (if assignees need to be set)

If you lack these permissions, cloning will fail or options may not appear.

Administrators can limit access to Epic Clone by:

  • Project scope (e.g. only allow usage from template projects)

  • Jira user groups (e.g. internal teams only)

This helps ensure consistent practices and avoids accidental cloning by unauthorized users.

  • Jira’s out-of-the-box clone only duplicates individual issues (epic or story) and doesn’t preserve downward hierarchy levels or relationships.

  • Epic Clone enables bulk, hierarchical cloning in one single operation.

  • It offers configuration before cloning (versus automation scripting) and is more flexible than alternatives like Jira Automation, which currently lacks robust support for nested hierarchies

Epic Clone is designed for scenarios where you need to:

  • Reuse structured epics as templates, including all stories, sub-tasks, and links.

  • Clone multiple issues (including hierarchy) in a single operation, without having to manually copy each item.

  • Clone into other projects while customizing fields like summaries, labels, or assignees per use case.

  • Perform bulk cloning without complex automation rules or scripting.

For teams who frequently build similar work packages (product releases, client projects, onboarding flows), Epic Clone streamlines what would otherwise require multiple manual steps or advanced Jira configuration.

No. Epic Clone works out-of-the-box. It automatically reads your existing field configurations for issues and epics.

There’s no need to build automation rules or scripts. You can, however, customize field mappings or apply find-and-replace actions during the clone process to fine-tune the cloned data as needed.

While Epic Clone doesn’t create new Jira projects itself, it allows you to set up a “template epic” (or a set of epics) in a designated project and then clone them into other projects as needed.

This is often used as a lightweight alternative to Jira’s native project templates, especially for teams who want more flexible control over issue structure and content. Furthermore, project templates populated with work items is an enterprise only feature at the moment.

Epic Clone supports standard Jira system fields as well as custom fields, as long as:

  • The target project has the same custom fields configured.

  • The user performing the clone has permission to edit these fields.

For unsupported or unmapped custom fields, Jira’s default values will apply in the cloned issues. You can review and adjust them during or after the cloning process.

As the number of child issues isn't limited in Jira, you can clone as many items at once as are listed in a parent item or the downward hierarchy levels.

No, you don’t need Jira Admin rights to use Epic Clone. Any user with the following can clone:

  • Create issue permissions in the target project.

  • Access to view and edit the issues you wish to clone.

Check out our other apps

Project Milestones for Jira

Define, plan, and schedule agile project milestones

Split long-running projects into phases for better project tracking in Jira. Perfect for classic project management, agile software development, and service management projects.

User Absence Planner

Don't let absences slow your team down

Out of office? Keep your team members informed by adding planned absence times like holidays or business trips to your Jira user profile, and even include a short message.

Deep dive into our approach

Epic Clone for Jira Cloud now includes a powerful REST API to automate cloning of issue hierarchies. Trigger cloning from scripts, external systems, or on a schedule. Boost efficiency with seamless Jira automation.
Discover the latest Epic Clone update for Jira Cloud, featuring background cloning for large epics and improved attachment handling. Work faster without waiting on dialogs.
Learn what the 'Run on Atlassian' badge means on Marketplace apps & why it matters for organizations with strict data governance and security requirements.