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

Bulk Sub-task creation through Plan creates issues in reverse order

XMLWordPrintable

      Issue Summary

      When viewing a Plan, you can create Issues in the Plan and then commit the changes to go ahead and create the Issues in Jira.  If you create several child Issues and then commit changes, the Child issues are created in reverse order, resulting in the child issues being shown in reverse order within the Jira issue. 

      Steps to Reproduce

      1. Navigate to a Plan. 
      2. Select the "Create Issue" option and create a Parent Issue.  We used the Task issue type. 
      3. Once the Parent issue is created, select the meatballs (...) next to the Task name and select "Create Sub-task".
      4. Create multiple Sub-tasks in a specific order (ie- Sub-task 1, Sub-task 2, Sub-Task 3). 
      5. Review Changes and Commit changes.  This will generate the Issue keys for these Issues.  
      6. The Issue keys are created in reverse order.  For example, if the Project key is ARJ, then the Parent Task would be ARJ-1 and Sub-task 3 would be ARJ-2, Sub-task 2 would be ARJ-3 and Sub-task 1 would be ARJ-4.
      7. Click on the Parent Task to open the Issue in full-screen.  The Sub-tasks are displayed in reverse order.  

      Expected Results

      The Sub-tasks will be assigned Issue keys in the order that they were created. 

      Actual Results

      The Sub-tasks are assigned Issue keys in the reverse order that they were created. 

      Workaround

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

              Unassigned Unassigned
              39c9abcf55e0 Rafael R
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: