Clone issues and all their subtasks

Kelli Frattini-Adams

 

I am trying to have a template of Epics, tasks and custom subtasks (Sub Test-Case), that I can clone by manually triggering an automation. I have the Epics being cloned and all child stories/tasks in one rule. But I am stumped with the second rule of creating the subtasks into the new created epic/issues. Please help! This is driving me mad. I've seen lots of posts on this but no real solution, at least not one that I'm following.

 

Stephen Wrathall_69gv73

Hi @Kelli Frattini-Adams

Doing a full deep-clone of Epics -> Tasks/Stories -> Subtasks is possible with Automation. It's not possible within a single rule because it requires 2 levels of branching, and only 1 branch is supported per rule. 

So the solution at a high level involves:

1. Rule 1: Cloning the Epic and all of it's Tasks/Stories
   1. While doing this, adding a temporary label to those newly-created Tasks/Stories
2. Rule 2: Cloning those newly-created Tasks/Stories's subtasks, based on the temporary label that was added.

If you don't set up the variables correctly, you can end up setting the wrong parent issues, or epic links. However both the solution, and examples of pitfalls are all covered in this lengthy community post here:

https://community.atlassian.com/t5/Jira-Software-questions/Re-Re-clone-an-epic-including-its-child-issues/qaq-p/2118393/comment-id/214327#M214327

Some scenarios aren't supported, e.g. cloning into difference Jira projects. If you have more complex requirements such as that, you may want to consider 3rd party apps like bulk clone or deep clone. 

I hope this helps.

Regards,
Stephen