How to copy an Epic template and its issues including the Linked Issues creating new linked issues
Asked by craig_hill:

Hello!

I'm looking for assistance with the best method to copy an existing Epic and all of the related sub-issues of that Epic as a new Epic such that it maintains all issues as well as all of the Linked Issues. However, I want the Linked Issues to be related to the newly created issues and not that of the template Epic issues.

I already have:

* An existing template Epic
* Automation to create a new Epic and all sub-issues as new issues

I do not have:

* How to create links for the new issues based on the template issue links

Someone had suggested adding labels on the issue that Blocks the Blocked by issue. This seems tedious and not overly maintainable. Each ticket needs the label added as well as updating the rule for each.

For example:

* Linked Issues
  * Issue A is blocked by Issue B
  * Issue C is blocked by Issue D

* Tag Template Issues:
  * Issue A tag = blocked-1
  * Issue B tag = blocks-1
  * Issue C tag = blocked-2
  * Issue D tag = blocks-2
* Automation (after the for-loop completes):
  * blocked would = "blocked-1"
  * the next if would be "blocked-2"
  * JQL would be updated to "blocks-2" for the label search
  * Keep going for the max number of relationships, if the template doesn't have any or only has a few, the if logic will fail to find the labels and skip that issue

I am not an administrator and will need to do this through the Jira automation UI. This is, at a high-level, how this is setup today.

![jira_automation_1.png](https://community.atlassian.com/t5/image/serverpage/image-id/338923i32B99C552EFD0B3E/image-dimensions/312x657?v=v2 "jira_automation_1.png")![jira_automation_2.png](https://community.atlassian.com/t5/image/serverpage/image-id/338924i8E244754DDA6BA26/image-dimensions/312x641?v=v2 "jira_automation_2.png")

Thank you for your assistance!


Answers:
author: John Funk
body: Hi Craig,

I would recommend the Deep Clone app in the Atlassian Marketplace.

comments: author: Marlene Kegel - codefortynine
body: Welcome to the community, [@craig_hill](/t5/user/viewprofilepage/user-id/5556682). And thank you for recommending [Deep Clone for Jira](https://marketplace.atlassian.com/apps/1218652?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2770676), [@John Funk](/t5/user/viewprofilepage/user-id/7148).

It's indeed possible and quite easy to copy an Epic Template with Deep Clone for Jira. You can [read more in our documentation.](https://documentation.codefortynine.com/deep-clone-for-jira/epic-tree-clone?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2770676)


author: Clara Belin-Brosseau
body: Hello [@craig_hill](/t5/user/viewprofilepage/user-id/5556682)

If you're seeking for an easier way to **clone issues with their linked issues** , you can try our app [Elements Copy \& Sync](https://marketplace.atlassian.com/apps/1211111/elements-copy-sync-clone-jira-issues?tab=overview&hosting=cloud?&utm_source=community&utm_medium=answer&utm_campaign=question_2770676&utm_keyword=CS&utm_vendorID=4952) that allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc).

![image (10).png](https://community.atlassian.com/t5/image/serverpage/image-id/339150i7A7C582C8BBBAF65/image-size/large?v=v2&px=999 "image (10).png")

You can check our guide [here](https://doc.elements-apps.com/copy-and-sync-jira-cloud/content-settings#Contentsettings-Copylinkstootherissues?&utm_source=community&utm_medium=answer&utm_campaign=question_2770676&utm_keyword=CS&utm_vendorID=4952).

The app is for **free during 30 days** (and it stays free under 10 users).


author: Elizabeth.Johnson
body: Hello,   

I have created 9 automations that do this.

1. Create Epic

2. Create Monthly Tasks and Assign them

- If any tasks were blocking each other and were right before/after each other then I add in the linking here.

3. Add in Checklists (spread over two automations due to length)

4. Add in the dependencies (spread over two automations)

Please let me know if you want more detail happy to help more.

![JIRA.png](https://community.atlassian.com/t5/image/serverpage/image-id/338943iA1F4D4D7ED38904F/image-size/large?v=v2&px=999 "JIRA.png")

<https://community.atlassian.com/t5/user/viewprofilepage/user-id/5556682>

<https://community.atlassian.com/t5/user/viewprofilepage/user-id/5556682>


author: Bill Sheboy
body: Hi [@craig_hill](/t5/user/viewprofilepage/user-id/5556682) -- Welcome to the Atlassian Community!

It is theoretically possible to use *several* automation rules to clone many parent / child issues and relink them correctly. Although, and IMO, such solutions are brittle as they are prone to timing problems from branching, waiting for issues to be created, handling errors, etc. The "trick" is ensuring all of the issues are created before any linking starts, and that often takes multiple rules executing over a window of time.

These difficulties are one reason why there are several marketplace apps to provide advanced cloning scenarios.

Another approach is to use a CSV import to create the issues, and then use an automation rule, checking things like those tags you described, to link them.

Kind regards,  
Bill


Tags: issue-link