Copy/Clone Epic, Tasks, Sub-Tasks, links 1:1 to a new Project

[Christian Mahlknecht]

Is it possible to "copy" or "clone" an epic with tasks and subtasks 1:1 into a new project in Jira Cloud, with an App or Automation? All links should remain the same and each task should be assigned to the epic and all Sub-Tasks to each Task as well. ?

I tried several apps but either the sub-tasks are not copied or the links refer to the old project or no epic is created. Can anyone help? Maybe with an automation?

Thanks

[Marlene Kegel - codefortynine · Accepted solution]

Hi Christian,

I'm the product manager of Deep Clone for Jira.

I've seen that you already contacted our support team. I hope your clone was already successful? 

For other readers :) 

You can clone an Epic along it's tasks and sub-tasks with our cloud app Deep Clone for Jira.

After you've installed Deep Clone you simply:

- Open the Epic

- Select Deep Clone from the actions menu of the Epic

- Select the desired target project ... and clone.

Don't hesitate to get in touch with us if you have feedback or questions.

[Christian Mahlknecht]

Hallo @Marlene Kegel - codefortynine 

sry for my late reply. Deep Clone is great and solves all our problems ;) I just wanted to ask in general if there is a free solution or if there is something already integrated in Jira Software.

[Marlene Kegel - codefortynine]

Thank you for your positive feedback, @Christian Mahlknecht ! It's great to hear, that Deep Clone for Jira solves all your problems :) 

[Andreas Bock]

The licence has to be bought, if we use it in our company to copy tasks? The function "clone" covers the same functionality but has a different meaning in the JIRA world.

[Marlene Kegel - codefortynine]

Welcome to the community, @Andreas Bock !

I am not sure if I understood your question correctly, but you don't need an extra Marketplace app to clone tasks in Jira.

Deep Clone for Jira offers advanced functionality that is not available in the basic clone feature:

• Bulk Clone several issues at once
• Clone Epics and their issues and keep the hierarchy
• Advanced Single Clone features, e.g. cloning comments
• ...

Does that help?

[Andreas Bock]

Hello @Marlene Kegel -codefortynine- ,

the question is: "Deep clone for jira" offers a free version. We can use it as a company? From which point on is it not free anymore? Christian asked the same question above. 

[Marlene Kegel - codefortynine]

Ah. Now I get it :)

Free trial means, you can test the full feature set of Deep Clone for Jira for free for 30 days. 

[Margarita Burkova]

Hi,
I solved this task as well and maybe it will be useful for someone else.

I ended up using two automations.

Automation 1
This automation rule is designed to allow users to manually clone (copy) a Jira issue along with all its child issues.

Main steps:

1. Clone the Parent Issue. The rule creates a new issue by copying key fields from the trigger issue
2. Store the Cloned Parent Key. The rule saves the key of the newly created parent issue in a smart value variable called cloneParent.
3. Clone Each Child Issue. The rule finds all issues whose parent is the original (trigger) issue. For each child issue: Stores the original child key in a variable (originalKey). Clones the child issue, copying fields similar to the parent, but sets the parent to the new cloned parent (cloneParent). Stores the new child key in a variable (cloneTask).Logs the mapping of original to cloned child keys.Sends a webhook with the mapping of original and cloned keys for further processing or integration.

Automation 2
This rule is designed to automate the process of copying all sub-tasks from an original issue to its newly cloned parent.

Main steps:

1. Trigger: The rule starts when Jira receives a specific webhook call. The webhook payload must include at least: originalKey (the key of the original parent issue), clonedKey (the key of the newly created/cloned parent issue)
2. Lookup the Cloned Parent Issue: the rule performs a JQL lookup to find the cloned parent issue using the key from the webhook: key = {{webhookData.clonedKey}}
3. Branch: For Each Sub-task of the Original Issue. The rule finds all issues whose parent is the original issue (parent = {{webhookData.originalKey}}).
4. Create Sub-task:
   Creates a new sub-task under the cloned parent (parent = {{webhookData.clonedKey}}), copying the fields from the original sub-task

[Jean Deson]

Hi all, 
Today i finish my automations for clonning entire EPIC with task and sub task. It takes me a little time but it's ok now.
The base is this.

First automation

• Clones the EPIC
• Clones all sub tasks (in the initials task)
• Clones the taks and put the cloned key in the initial task in a free new field

Second automation

• for updated new field in the initials task
• update the new subtacks (not the initials, for me filtered by component) with the value of the new reference task

Third automation

• for updated new field in the finals subtask (filtered by component)
• update the parent with 
  

  { "fields": {"parent": {"key": "{{issue.newField}}"}}}

This way is because updating parent link not works in a nesteed loop from parent level. 

note that i dont put all details of cleaning components and other fields.