How to clone a Task with all its sub-tasks and dependencies from another project under current epic

Munir Patel May 2, 2024

I have a task and underneath sub-tasks with dependencies in a project A

I need to clone this task with subtasks under current Epic in project B

How can I make it simple for a user to add as and when they need.

1 answer

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 2, 2024

Hello @Munir Patel 

The user can use the current Clone Issue function to clone the issue and it's subtasks in the same project. They can then use the Move function to move the parent task to the other project. And then the user can associate the moved issue to a different Epic 

You could potentially build an Automation Rule that would handle all of that which a user could trigger manually and which would prompt the user for the key of the Epic to which the new issue could be added.

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

Munir Patel May 2, 2024

I created below automation and when running for a Task to clone the Task and all its subtasks it clones only the task and no subtasks is cloned.

Clone Automation.JPG

Munir Patel May 2, 2024

Please ignore above message I corrected issue type as subtask and it worked. thanks

 

Munir Patel May 2, 2024

The cloning of subtasks is not in same sequence as under the original tasks. Is there a way to ensure the subtask is shown in same sequence as in original

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 2, 2024

Please show us your current rule with the details of each step.

Munir Patel May 3, 2024

Please find enclosed Slide1.JPGSlide2.JPGSlide3.JPGSlide4.JPGSlide5.JPG

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 3, 2024

Hello @Munir Patel 

With the For Each option I don't believe it is possible to dictate the order in which the sub-tasks are cloned and added to the previously created issue.

I think that you could instead use a Lookup Issues action to retrieve a sorted list of the sub-tasks of the original issue, and then use a branch to step through that sorted list to clone the sub-tasks in order. I have not actually tried that yet. There is a discussion of using a For Each branch to iterate over the results of a Lookup Issues action in this post:

https://community.atlassian.com/t5/Jira-questions/Use-lookupissues-to-then-clone-those-issues-and-their-sub-tasks/qaq-p/2263298

Suggest an answer

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

Atlassian Community Events