Clone Epic, Stories and Subtasks tree with Jira Automation

[Daniel Wynne Walters]

Hi I am still having issue where the task still has the old key in the summary is there anything to get rid of that old key.

[Guy Anela]

Here's another solution that doesn't require you to prepend the issue key to the Summary of the original issue and later parse it out. It simply uses an Incoming Webhook Trigger to create the Sub-task level children on the fly. :) 

As with the original solution, this one uses two separate Automations:

1. The first Automation is Manually triggered. It simply Clones the Epic and it's direct children. As it's looping thru the children, it will fire off a Send Web Request Action to Clone the Sub-task level children (if any exist).
   
   
   
   NOTE: Make sure the Header Key is set to  "X-Automation-Webhook-Token" and the Value is the Secret found in the Trigger of the second Automation. The Web Request URL can be found in the Trigger of the second Automation as well.
   
   
2. The second Automation Rule uses an Incoming Webhook Trigger...
   
   
   
   

Anyhow, I hope this helps. Cheers!

[Vries, E. de (Elske)]

Thanks for this very helpful solution. I've been looking for a solution for a long time. 
I got it working, but I see one thing i need to fix. I hope someone can help me out. 

I have a set of stories underneath my Epic. A few of these stories are linked to each other with "linked issues" option. 

When I clone my Epic + all stories. The stories are all copied, but the "linked issue" shows a link to the source story. I need a link between the stories of the copied set. 

Set of source stories:
ID1 - Linked to ID2
ID2 - Linked to ID1

New set of copied stories (in my current automation):
ID3 - Linked to ID2
ID4 - Linked to ID1

Wanted result:
ID3 - Linked to ID4
ID4 - Linked to ID3