Clone Epic, Stories and Subtasks tree with Jira Automation

52 comments

Daniel Wynne Walters
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 27, 2025

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
Contributor
February 27, 2025

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).

    CLONE EPIC AUTOMATION IMG1.png

    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...

    CLONE EPIC AUTOMATION IMG2.png

Anyhow, I hope this helps. Cheers!

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events