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
Community Members
Community Events
Community Groups

How clone a task and its subtasks ?


I don't have the subtasks when I clone a task with subtasks. Is it possible to do it ?

8 answers

1 accepted

4 votes
Answer accepted
Ben Stuart Atlassian Team Apr 30, 2020

image (2).pngThis configuration will clone the sub-tasks when you're cloning based on a trigger. 

It really worked..  !! Thx :) 

Hi, @Ben Stuart -

When I try this (in Jira Cloud Premium), the new Sub-task shows up among the children of the original Task rather than the children of the Task's new clone. I can verify it in the XML export of the new Sub-task; i.e., the key in the <parent id="integer">key</parent> node is that of the original Task. 

In a subsequent Edit Issue action, I modified the parent attribute in the Advanced Field editing control by creating a variable 'myParentKey' then using the JSON { "parent" : "{{myParentKey}}" }. I verified that it succeeded: the XML export of the new Sub-task had the parent node set to the new Task's ID and key.

However, the new Sub-task clone still shows up in the original Task's children.

Can you please verify that your suggestion from April 30 2020 still works?


Buenas tardes,

Si necesitan clonar subtareas de un issue especifico a otro, pueden hacer lo siguiente:clone.png

¡Me funcionó bien!


Hello Nick,

Thank you for your answer.

Hello Nick,

I did it with 2 rules but I have an another problem...The subtask have links between them (block by etc...) and when I clone the subtasks the links are not clones...I lost all my links, too bad.

Do you have an idea.

Unfortunately we can't clone issue links yet.

We are tracking this at:

You can add the links to the description of the issue or asa comment, not perfect but it is workable.




I need to do the same and wanted to know which combination of rules you used to clone botht the issue and the subtasks?

Hello Nick,

It in not exactly what I would like to do. 

"When I create an issue A then I clone an issue B and for this issue I clone their sub-tasks...and I delete the issue A"

But I can not add "And:For Sub-tasks" in the JQL branch...

See the the screen shot below2017-08-28_0933.png

Hello Nick,

I'm sorry to answer you so late...

I've tried to do what you told me but it is too difficult...I'm not an expert yet in the pluggin settings.

For example...I have a trigger "When: Issue commented" and an action "Then: Clone issue into same project and same issue type"...after that I don't know what to do to clone the subtasks of the task...sorry.




I tried the following locally and it succesfully craeted clones sub-tasks.

Screen Shot 2017-07-21 at 3.16.12 pm.png

Let me know if you get it working.




@Nick Menere 

Hi Nick, 

I came across this awesome workaround when looking for options to clone a task along with it's children. Unfortunately, when I try the same rule with the given advance settings, I'm getting the following error for sub tasks cloning piece.

Error - creating issueIssue type is a sub-task but parent issue key or id not specified. (issuetype)


Could please assist me on this? 

Hi Anil,


Best to raise a support request with this one so we can figure it -




Was this issue ever resolved? I'm successful when attempting the above, but I'm seeing that the resulting subtasks are created in the reverse order as compared to the original list, which is problematic for our use case. In attempting to overcome this using JQL to 'force' the Rank order, I then get the same error message Anil reported.


@Anil kumar Bondada @Nick Menere @Ben Stuart 

Like # people like this

@Nick Menere you're awesome, thank you!

0 votes



We are tracking the ability to clone subtasks automatically at - AUT-335

In the mean time, you can mnaully loop over the sub-tasks of the original issue and clone these. You will need to overwrite the parent in the advanced section with:

    "fields": {
        "parent": "{{createdIssues.first.key}}."

This will set teh parent of teh cloned issue to the first issue created in the rule - in this case the original clone.


Let me know how you go.




Hello Nick,

Unfortunately, this (great) workaround no longer works. It now returns an error to the Audit log:


Error creating issue Issue type is a sub-task but parent issue key or id not specified. (issuetype)



There are a number of add-ons that can do this, with varying features.  You will need an add-on of some sort to do this, though.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events