Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-75739

Cloning issue with sub-tasks in a next-gen project, reverses the ordering of subtasks

XMLWordPrintable

      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

      1. Create a next-gen issue with subtasks.
      2. 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.

      • Original:
      • Clone:

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

        1. Clone.png
          Clone.png
          115 kB
        2. Original.png
          Original.png
          118 kB

            [JRACLOUD-75739] Cloning issue with sub-tasks in a next-gen project, reverses the ordering of subtasks

            Matthew Hunter made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            Matthew Hunter made changes -
            Labels New: timeout-bulk-close202112

            Matthew Hunter added a comment -
            Atlassian Update - December 16, 2021

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - December 16, 2021 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team
            Andrew T made changes -
            Component/s New: Issue - Create - ChildIssuePanel [ 62792 ]
            Component/s Original: Backlog (Next-gen) - Issue Create [ 62206 ]
            Key Original: JSWCLOUD-20936 New: JRACLOUD-75739
            Project Original: Jira Software Cloud [ 18511 ] New: Jira Cloud (including JIRA Core) [ 18514 ]
            tchen made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Renaud Tertrais made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 518083 ]
            raymo made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 515790 ]
            Joanne Griffin made changes -
            Comment [ This is also effecting my team.

              ]
            raymo made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 514850 ]
            Willow Yang (Inactive) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 515002 ]

              Unassigned Unassigned
              prawat@atlassian.com Prashant R (Inactive)
              Affected customers:
              3 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: