Issue rank in a sprint may change after page refresh

Issues moved to a sprint appear in a different order once the page is refreshed.

—

Original summary

Dragging the first issue to a sprint does not update its rank properly

Original description

When you drag-and-drop the first issue in a sprint, the ranking is not updated.
Then when you start adding more issues to that sprint, all these issues will "clump" around the first issue's original raking.
This also happens if you use the "+ Create issue" button at the bottom of the sprint to create the first issue of this sprint.

End result is that sometimes the ranking of issues viewed via a filter result page does not look like what you see on a board's backlog view.

We have people (tech writers, managers) looking at issue priorities with via filter result pages or dashboards. It's very difficult and time consuming to have to manually groom the issue ranking to "mimic" the board's backlog view.