How to clone Epic with all its issues preserving same linkage on cloned Epic and cloned issues?

[Rim Budrys]

1. Created an Epic with 2 child issues.
2. Used "Clone an Epic from one company-managed project to another with all existing issues" buit-in automation template
3. Used the following config (see screen print)
4. Got Epic and 2 child issues cloned, but issues are orphaned and not linked to cloned Epic . What settings would achieve cloned issues to be auto-linked to cloned epic to mimic the original Epic to issue relationship?

[Thibaut Subra _Elements_]

Hi @Rim Budrys 

If you need to go further, we developed an application called Copy & Sync that allows you to copy an Epic with all its child issues with a single recipe.

In a nutshell, you will be able to:

• Copy an Epic with all its child issues
• Copy subtasks of the child issues if any
• Choose which fields you want to copy (summary, description, etc.), but also comments, attachments and so on
• Keep all links between the Epic and its child issues

It's really easy to use and to configure with just a few clicks.

If you want to keep your Automation, you can trigger the recipe directly via Automation through API.

Feel free to give a try, it's free under 10 users and we have a 30-Day trial policy.

I'll be glad to help!

Regards

Thibaut

[Syed Majid Hassan -Exalate-]

HI @Rim Budrys

Welcome to the community. This is Majid @ Exalate. 

I am not sure if you were able to solve this or not, but using a synchronization solution liek Exalate you can sync these Epics bi-directionally to another Jira project (on the same instance) or a totally different Jira system as well. 

Hope it helps. 

Thanks

Majid

[Luka Hummel - codefortynine]

Hi @Rim Budrys and welcome to the community!

If you are willing to use a third-party app, our Deep Clone for Jira can help you clone whole issues hierarchies (Initiatives ⇒ Epics ⇒ Tasks/Stories ⇒ Subtasks) with our Epic/Tree Clone feature.

1. Navigate to the issue you want to clone

2. Click Action menu ••• > Deep Clone

3. Select Epic/Tree Clone

4. Configure and create your Epic/Tree Clone

Soon, you will also be able to create presets for Epic/Tree Clones, so you will be able to quickly trigger an Epic/Tree Clone from the Actions menu ···. This will also allow you to trigger an Epic/Tree Clone via Jira automation.

We even have planned a webinar to introduce the feature. You can sign up here if you are interested.

[Mark Segall]

Hi @Rim Budrys and welcome to the community!

Right now your child issues are cloning but with "Copy from Parent", it means they are attempting to copy the Epic Link of their parent which doesn't exist yet.  Here's how I would address it:

Add a Create Variable action just after your Epic clone:

• varEpic
• {{createdIssue}}

Then in the Clone Issue within your branch, change Epic Link from "copy from parent' to {{varEpic}}

[Rim Budrys]

Unfortunately {{varEpic}} cannot be set in Epic Link field in UI considering it is a dropdown.

I was able to get cloned tasks to be linked to new cloned epic via "Relates" 

However I need new cloned tasks to have a newly cloned epic as their parent instead.

[Mark Segall]

You can absolutely use a smart value in the Epic Link field.  As you start typing it in, you will be prompted to use it as a smart value.