Duplicate Epic Cloud Documentation

What does Duplicate Epic do?

With Duplicate Epic you get the additional functionality to clone an epic together with all issues in epic. The standard clone functionality in Jira only lets you duplicate the issue with (optionally) attachments, links or sub-tasks. For epics, issues which are linked to the epic by the epic link or parent field can't be copied together with the epic within the same clone process.

How can Duplicate Epic be used?

After installation of the app you will see an additional entry in the issue actions (three dots in the top right corner). It is called "Duplicate Epic" and only visible in issues of type epic.

If you click on that entry, the duplicate epic screen will open.

What you can do on the Duplicate Epic screen?

If you duplicate epics in Jira Cloud with Duplicate Epic, a dialog will be displayed where you can make your configuration of the duplicated epic. Let's assume we want to clone this issue with Duplicate Epic:

It contains 3 child issues and 2 linked issues. If you now select the three dots → Duplicate Epic you will get this duplicate epic dialog.

Summary: Set the summary for the duplicated epic. The summary of the source issue is displayed by default.

Clone links: If the epic is linked to other issues, you will see a toggle to optionally include the links when duplicating. If enabled, the linked issues are displayed and after duplication is completed the linked issues to the source epic will also be linked to the duplicated epic.

Clone attachments: If the source epic or one of its child issues has attachment(s) and if you have create attachment permission in the project, you can decide if you want to clone the attachments or not. By default, it is selected to clone attachments. If the field doesn’t appear, it either means that the source epic and its child issues don’t have attachments, or that you don’t have the permission to add attachments in the project. If enabled, the attachments will be copied for the epic and all issues in epic and subtasks which have attachments.

Duplicate child issues in source project: If at least one of the child issues in Epic is from a different project than the epic itself, you can decide whether you want to duplicate the issues in epic in the same project than the epic, or if you want to keep all child issues in their source project.

Here is an example:

• Epic in Project DEV

  • child issue 1 in project DEV

  • child issue 2 in project DEV

  • child issue 3 in project KANBAN

Duplication with the toggle enabled:

• Epic in Project DEV → Duplicated Epic in Project DEV

  • child issue 1 in project DEV → Duplicated issue 1 in Project DEV

  • child issue 2 in project DEV → Duplicated issue 2 in Project DEV

  • child issue 3 in project KANBAN → Duplicated issue 3 in Project KANBAN

Duplication without the toggle enabled:

• Epic in Project DEV → Duplicated Epic in Project DEV

  • child issue 1 in project DEV → Duplicated issue 1 in Project DEV

  • child issue 2 in project DEV → Duplicated issue 2 in Project DEV

  • child issue 3 in project KANBAN → Duplicated issue 3 in Project DEV

Issues in Epic: The issues in epic of the source epic are listed. By default, all issues in epic are checked. Issues which issue type isn’t available in the project are disabled and can’t be selected. You can decide for each issue in epic if you want to duplicate it together with the epic or not. Just uncheck the checkbox for an issue to skip it.

If you click on submit, the duplication is started. During duplication you can see the progress and how, step by step, the issues are copied. On the left, the source issues are displayed, in the middle you see a spinner when duplicating is not completed and a icon if it’s done. On the right side you see a link to the new issue and can directly navigate to it (link opens in a new tab).

On top you see the issue that is currently in progress either for copying, or setting a link to the new parent issue.

When duplication is completed, you can quickly navigate to each source or target issue by using the displayed links.

App usage statistics

For Jira system administrators only: https://ij-solutions.atlassian.net/wiki/spaces/DEC/pages/1014104070