The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Child issues

Deleted user
October 20, 2020

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?

 

J1.jpgJ2.jpg

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 23, 2020

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

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events