Child issues in random order after cloning

[Deleted user]

When we clone an epic the child issues are then displayed in a different order than the original epic. Anyone else had this issue?

[Angélica Luz]

Hello Tony,

Thank you for reaching out to Atlassian Community!

When cloning an issue in Jira, the child issues are not cloned, so based on a question that you posted a while ago, I would like to confirm the steps you are following. 

When you say Child issues, do you mean the "Issues in this epic" or "Linked issues"?

Are you using the add-on mentioned in your previous question or the Clone feature in Jira?

Regards,
Angélica

[Deleted user]

Hi Angélica

No this is not connected to the previous question that i asked. When I clone an epic, I have the boxes ticked to clone issues of the epic and clone subtasks of the epic and its issues and then the subtasks are cloned but not in the same order as they are in the original epic that I have cloned from

I hope this helps

Thank you

Tony

[Angélica Luz]

Thank you for the details, Tony, and sorry for the misunderstanding. I was using the new issue view where it's not possible to create sub-tasks, so I thought that it was related to "Issue in this Epic".

Using the old view, I added some sub-tasks on the Epic and changed its order. After cloning, it was on the same order as the original Epic. In my case, I had 4 sub-tasks only.

How many sub-tasks there are on the Epic you are cloning? 

Is it happening on all Epics that you clone?

[Deleted user]

Well when we clone the Epic the child issues are in then in wrong order in the cloned epic, when we then clone that clone it then corrects the order of the child issues, which is extremely bizarre. We have tested this on multiple epics with various numbers of child issues and we get the same issue. See below

[Marlene Kegel - codefortynine]

Hi Tony,

I remember that we were in touch in another Community thread :)

Does this issue occur when you clone with with our Marketplace app Deep Clone for Jira? If yes, can you get in touch with our support? 

Thank you!

Marlene

[Angélica Luz]

Thank you for the screenshots, Tony.

I can see that your site administrator created a ticket with our support and they are investigating the issue. It seems that it happens when cloning the child issue of an Epic and not the Epic itself.

Since our support is able to access your site, let's wait for their response to avoid any possible misunderstandings. Once it's resolved, feel free to share the resolution here to help other community members that may have the same question.

[Marlene Kegel - codefortynine]

Hi Tony,

If you're working with Deep Clone for Jira, the issue should be solved by now. We released an update yesterday that remains the ranking of original subtasks when they're cloned.

Let me know if something doesn't work as expected.

[Deleted user]

Hi Marlene

Thank you for your message, we are not using the Deep Clone for Jira this issue is with Jira and we have a ticket raised which has been escalated as the can only replicate the issue in our Jira.

[Marlene Kegel - codefortynine]

Thank you for the update, Tony!