Issue Summary

When a sprint is started sometimes:

• The Active Sprints tab shows no work items or just a fraction of them
• JQL `Sprint in openSprints()` returns the same list, even though the sprint is already open

What is still working in that case is:

• In the Backlog view the sprint can be completed like any other started sprint
• JQL `Sprint in XYZ-123` works fine and returns all work items
• Work items are still assigned to a correct sprint

Steps to Reproduce

There hasn't been a reliable way of reproducing this issue, as it might be related to a race condition. A common pattern is this in a very fast fashion:

1. A sprint is moved using "Move sprint up" or "Move sprint down" button in the Backlog view. It can probably be some other operation on a sprint too, like rename
2. A sprint is started using "Start sprint" button

What happens then is an out of order processing:

• event about starting a sprint is processed first
• event about sprint being moved is processed second, and because only future sprints can be moved its status is replaced

Expected Results

All work items that are in open sprints are visible in Active Sprints tab and are returned after running `Sprint in openSprints()` JQL.

Actual Results

Only a fraction of expected work items are visible in Active Sprints tab are returned after running `Sprint in openSprints()` JQL.

Workaround

To make all work items be considered as in open sprint do either:

1. Edit sprint, for example change its name. Then you can change it back.
2. Remove work items from the broken sprint and add them back.