Global Automation: Clone Task and sub-task and maintain child issue relationship
Asked by Cl?udia Silva:

Hello,

I created an automation in which when there is a change in an issue (Field Released? = Yes) then we will go to issues "is validated by" and we will clone all existing ones, both those of the "Test Case" type and the "Sub-task" type " however you are sub-task so surely associated with a "Test Case". What I wanted was that when the test case was cloned it would also clone the child issues, but from what I researched this is not possible.. so what I was doing was cloning everything that was in the "is validated by" section, that is both tasks and sub-tasks but I wanted when I opened the clone of the task that child issues appeared, which are clones of the sub-tasks but that doesn't happen, it just cloned each one without any relation..

<br />

It's possible?

![Clone Child.png](https://community.atlassian.com/t5/image/serverpage/image-id/325049i9FE9B9E64E2D5D0D/image-size/large?v=v2&px=999 "Clone Child.png")

![Linked Issues.png](https://community.atlassian.com/t5/image/serverpage/image-id/325044i5F2D0E602FFB92DA/image-size/large?v=v2&px=999 "Linked Issues.png")

Thank you!!


Answers:
author: Clara Belin-Brosseau
body: Hello [@Cl?udia Silva](/t5/user/viewprofilepage/user-id/5056478)

If you're willing to use a third-party application, I can suggest trying our app [Elements Copy \& Sync](https://go.elements-apps.com/cs_2405_3) that allows you to copy issues with all their content (summary, description, custom fields, comments, attachments, etc.) and their child issues.

You'll be able to [easily clone tasks with their subtasks](https://go.elements-apps.com/cs_2405_4) (and it's compatible with Jira Automation).

Don't hesitate to try our app, it's free during 30 days and stays free under 10 users.

Kind regards,  
Clara

comments: author: Cl?udia Silva
body: However, I managed to solve it in another way, but thank you very much for your help and recommendation [@Clara Belin-Brosseau](/t5/user/viewprofilepage/user-id/5326232) !


author: Luka Hummel - codefortynine
body: Hi [@Cl?udia Silva](/t5/user/viewprofilepage/user-id/5056478)

While Jira's native automation capabilities are powerful, they do have some limitations, particularly when it comes to complex cloning operations that maintain hierarchical relationships.

If you are willing to use a third-party app, our [Deep Clone for Jira](https://marketplace.atlassian.com/apps/1218652?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2704200) could help you. This app provides advanced cloning features, including the ability to clone entire issue hierarchies, thus preserving the parent-child relationships between tasks and subtasks.

While Deep Clone for Jira provides manual cloning capabilities, you can also use it in conjunction with Jira automation rules and [trigger a Deep Clone as part of your Jira automation](https://documentation.codefortynine.com/deep-clone-for-jira/jira-automation?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2704200).

comments: author: Cl?udia Silva
body: However, I managed to solve it in another way, but thank you very much for your help and recommendation [@Luka Hummel - codefortynine](/t5/user/viewprofilepage/user-id/5127666) !


Tags: cloud

jira-service-management

jira-service-management-cloud