Issue Summary

This is reproducible on Data Center: (yes)

• The sprint sorting is done in backend by compounding sequenceid and id of the sprint with priority to sequenceid
• In new cloud, sequenceid column is null by default and is generated when an ordering is done in the board
• When fetching the sprints, backend does this :  sequenceid=sequenceid==null?sprintid

• This orders the list in unfriendly ways because the id of sprints in the cloud for this customer has started to overlap with sequenceid of older sprints in the server. 

Steps to Reproduce

• Create project and board
• Add sprints to the board and complete them
• Verify sprint order in burndown chart on Jira Server
• Run S2C migration
• Verify sprint order in burndown chart on Jira cloud

Expected Results

Burn-down chart displays sprints in the same order as the server after S2C migration. 

Actual Results

Sprint order is burndown chart is not same as that in the server which leads to newer sprints going down in the dropdown. Since customer can't find their sprints at the top of the dropdown, they feel that the sprint is not migrated whereas it can be found somewhere at the end of the list. 

Additional Context

Users may also identify this when creating new sprints after the migration. Sprint name suggestions don't increment as expected after the migration of Jira project that has an active sprint.

Workaround

Currently, the workaround for this issue is to modify the AO_60DB71_SPRINT table to restore the Sprint ordering. 

Details steps are provided in the page below - 

https://hello.atlassian.net/wiki/spaces/IDE/pages/1250018722/JST-663802+-+Database+Patch+Runbook