You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Currently, there is no way to directly clone the stories and subtasks under an Epic in Jira. Indeed there is a feature request in place to add this functionality:
As a workaround, you can use Jira automation to solve this problem. For this, you will need to create the next two automation rules in your project:
Clone the Epic
Save the epic ID
Clone each child linking the new issue to the new Epic, and append the original issue key to the newly created issue; this will help to identify the issue in the next rule to clone the subtasks.
Since the result of the 1st rule will trigger this new rule, you need to enable the checkbox shown below:
Create a variable to know from which original issue the new issue was cloned.
smart value: {{issue.summary.replaceAll("(.*key:)","")}}
Remove the old key from the summary string:
smart value: {{issue.summary.replaceAll("(key:.*$)","")}}
Look for subtasks from the original issue:
Clone each subtask, selecting the trigger issue as the parent:
If you need to clone the issue links or the attachments you can add the fields in the clone action as follows:
Please note some elements can't be cloned, like the history, comments, or logged time.
I hope that this article is useful for you and helps to improve your team's productivity using Jira and Jira Automation.
Jorge H
4 comments