Child issues

[Deleted user]

When we clone an epic we find the order of the child issues are in in a different order once the epic has been cloned. Anyone else had this issue as we haven't seen this before? See images why is this happening?

[Bill Sheboy]

Hi @[deleted] 

I hypothesize that because this is Jira Cloud, and that most of the actions with pieces (copy, clone, automation rules, complete sprint, etc.) run asynchronously, that there is no guarantee of ordering. 

I did a quick check and did not see any open defects for this symptom in the public cloud backlog, but found one for server version: 

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

Best regards,

Bill