Summary

When Sprints are reordered in a SCRUM Backlog prior to being started, they are assigned a 'SEQUENCE ID' that takes presedence over the 'SPRINT ID' when ordered running sprints. This causes a large amount of confusion to Users as well as Project Administrators as the SCRUM UI does not offer any indication as to why the ordering is not appearing as one would assume it should.

Environment

Cloud - 1000.350.1
Server - Current

Steps to Reproduce

1. Create a new SCRUM Software Development Project
   or
2. Open an existing SCRUM Software Development Project
3. Create several sprints (you do not need to add issues to the Sprints)
4. Start at least one Sprint
5. Reorder several of the remaining Sprints within the backlog
6. Start the remaining Sprints

Expected Results

The Sprints should follow the order in which they were started

Actual Results

The Sprints follow the order in which their SPRINT IDs and if populated, their SEQUENCE IDs follow

Example:

jira=> select * from "AO_60DB71_SPRINT" where "NAME" like '%TSSI%';
 CLOSED | COMPLETE_DATE | END_DATE | ID |     NAME      | RAPID_VIEW_ID | SEQUENCE | STARTED | START_DATE | GOAL
--------+---------------+----------+----+---------------+---------------+----------+---------+------------+------
 f      |               |          | 33 |    Sprint 1   |            30 |          | f       |            |
 f      |               |          | 34 |    Sprint 2   |            30 |          | f       |            |
 f      |               |          | 35 |    Sprint 3   |            30 |          | f       |            |
 f      |               |          | 36 |    Sprint 4   |            30 |          | f       |            |
(4 rows)

The above table shows the Sprints prior to being started and reordered in the Backlog. Notice there is no SEQUENCE ID populated for any of the Sprints.

jira=> select * from "AO_60DB71_SPRINT" where "NAME" like '%TSSI%';
 CLOSED | COMPLETE_DATE | END_DATE | ID |     NAME      | RAPID_VIEW_ID | SEQUENCE | STARTED | START_DATE | GOAL
--------+---------------+----------+----+---------------+---------------+----------+---------+------------+------
 f      |               |          | 36 |    Sprint 4   |           30  |       35 | f       |            |
 f      |               |          | 34 |    Sprint 2   |           30  |       36 | f       |            |
 f      |               |          | 33 |    Sprint 1   |           30  |       34 | f       |            |
 f      |               |          | 35 |    Sprint 3   |           30  |       33 | f       |            |
(4 rows)

The above table shows the Sprints after being reordered. You will notice that the Sprints all have SEQUENCE IDs populated now which fall in line with their updated position in the overall order of Sprints. After starting all of these Sprints the SCRUM UI would render them in this order:

Sprint 3
Sprint 1
Sprint 4
Sprint 2

Feature Request

It would be extremely helpful if it was possible to do one or all of the following within the SCRUM UI Backlog:

• Reorder Sprints once they have been started
• The ability to change the SEQUENCE ID of each Sprint
• The ability to see the SEQUENCE ID in relation to the SPRINT ID
• JIRA ordered solely based on the SEQUENCE ID and did not take the SPRINT ID into consideration in this case