-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Minor
-
Issue Summary
The ordering of the sub-tasks in the clone issue gets reversed when you clone a next-gen issue with its sub-tasks.
Steps to Reproduce
- Create a next-gen issue with subtasks.
- Clone it with the subtasks
Expected Results
The ordering of the sub-tasks' clones should be same as that in the original issue.
Actual Results
The ordering of the subtasks' clones are rather reversed.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
[JRACLOUD-75739] Cloning issue with sub-tasks in a next-gen project, reverses the ordering of subtasks
Resolution | New: Timed out [ 10 ] | |
Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
Labels | New: timeout-bulk-close202112 |
Component/s | New: Issue - Create - ChildIssuePanel [ 62792 ] | |
Component/s | Original: Backlog (Next-gen) - Issue Create [ 62206 ] | |
Key |
Original:
|
New:
|
Project | Original: Jira Software Cloud [ 18511 ] | New: Jira Cloud (including JIRA Core) [ 18514 ] |
Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 518083 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 515790 ] |
Comment |
[ This is also effecting my team.
] |
Remote Link | New: This issue links to "Page (Confluence)" [ 514850 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 515002 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 513460 ] |