Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,455,281
Community Members
 
Community Events
175
Community Groups

How to Clone an Epic with Tasks and Subtasks

What I want:

Clone following Epic with following structure of Tasks and Subtasks (inside a Team-Managed Project):

capt1.png

 

What I have so far: 

Via Automation, I get the Epic Cloned and also the Tasks but I cannot get the subtasks too:

CAPT8.png

Automation Logic:

capt2.pngcapt3.pngcapt4.pngcapt5.pngcapt6.pngcapt7.png

2 answers

2 votes

Hello @Nacho García-Robledo 

If you don't mind testing an add-on, Elements Copy & Sync lets you do exactly that.

Full disclosure, I'm the Product Manager of the app.

With our app, you will be able to clone Epics with all their issues, including subtasks, and keep the hierarchy.

It is as easy as clicking on two options, which are explained in our tutorials:

The app is free for 30 days, (and stays free if your instance is under 10 users), so feel free to give it a try, and don't hesitate to tell reach our Support if you have any question.

Kind regards,

Julien

Thanks @Julien Peyrade _ Elements , unfortunately we are not allowed to bring any add-on which has an impact on cost.

In any case thanks for your time!

That's perfectly understandable, you're welcome. :)

0 votes
Trudy Claspill Community Leader Jan 25, 2023

Hello @Nacho García-Robledo 

Please show the rule Audit Log details for an execution of this rule where the subtasks are not cloned.

Hello @Trudy Claspill , here it is the log file:

Captura de pantalla 2023-01-26 092507.png

 

as per my understanding I have here 2 problems:

1. The variable is not taking really the key for the subtask as it takes the one for the issue that triggered the point

2. it does not iterate, therefore it will generates only 1 subtastk

Trudy Claspill Community Leader Jan 26, 2023

Between 2 and 3 you are starting a branch to iterate through the child issues of the Epic. The branch clones the child issues.

Between 3 and 4 you have a Condition to check for Subtasks. A Condition is not a Branch, so there is no iterating over the Subtasks in the original child issue that was cloned.

Automation for Jira does not currently support having a Branch within a Branch. So, within the iteration of cloning child issues you cannot add another branch to iterate over the original issue's subtasks and clone them also.

I have not worked out all the details, but I believe you may need a separate rule to clone the subtasks. I'm sure there are other posts in the Atlassian Jira communities on this topic. If I find one that presents the solution, I'll post a link.

Trudy Claspill Community Leader Jan 26, 2023

This post includes an answer where the person does the cloning in two rules. A status change triggers the rule, but you could modify that trigger to something else.

I have not worked through the automation rule myself, so I can't attest that it works as written. If you try to replicate the two rules and run into trouble, post what you have and we can help debug.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events