Sub-tasks in reverse order after cloning epic.

[Mateusz Slifirczyk]

Hi all,

I am having a strange issue, where upon cloning an epic, the sub-tasks are cloned in reverse order. I thought at first it might be a problem with this one epic, so I've created a new one within the project and tried cloning that one, but it's still happening.

Any ideas what could be causing this?

[Bill Sheboy]

Hi @Mateusz Slifirczyk  -- Welcome to the Atlassian Community!

My experience and best guess is that clone's adding issues happens asynchronously, and so there is no guarantee of the sub-task (or other child item) ordering when added.

There is an open suggestion to fix this for the server version.  I couldn't find the one for cloud, even though this is clearly an issue for clone and clone via automation rules for cloud.

https://jira.atlassian.com/browse/JRASERVER-69617

Best regards,

Bill