Can I keep subtasks status when cloning their parent?

[Elvin Badalov]

I have a story with 20 subtasks. Some of the subtasks are in Done, some in In Progress, and some are in To Do status. 

If I clone the parent (the story) along with all of its subtasks, all the cloned subtasks end up in the To Do status in the cloned story. Is it possible for the subtasks created as a result of cloning to match the statuses of the original subtasks?

[Petter Gonçalves]

Hello @Elvin Badalov

Thank you for reaching out.

Indeed, the status od sub-tasks are not retained when cloning issues.

We understand that it can be a cumbersome process to change the statuses of all cloned sub-tasks, so we created the following feature request to allow the ability to retain the sub-task status when cloning it:

As a User, I want JIRA to give us the option to retain status when cloning or splitting an Issue. 

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

Let us know if you have any questions.

[Elvin Badalov]

Thanks for your response. While we're waiting for that feature, do you know whether this would be possible using Automation for Jira? I cannot find a way to contact the Automation for Jira team to ask this question. 

[Petter Gonçalves]

Hello @Elvin Badalov

You are welcome.

Indeed, I was trying to identify if there was a way to achieve that using Automation for Jira, however, no links or connections are created between the sub-tasks of the cloned issues in Jira, so I'm afraid there is no way to identify and copy the fields from each cloned sub-task.

Anyway, I believe that Automation for Jira would be the most complete tool to make that integration work, we would just need a feature to a link the cloned sub-tasks, just like to parent does (Cloned by). I'll make sure our PMs have access to this information in the feature request.

In the meaning time, keep an eye on the mentioned feature request to receive any updates from our PMs and developers. Thanks!

[Marcel Reinieren]

It could be so simple, just allow to copy status field when cloning. The jira ticket is hard to find so it does not get many upvotes. Many of my collegue scrummasters would like to have robust cloning automation.