-
Bug
-
Resolution: Fixed
-
High
-
63
-
Severity 3 - Minor
-
25
-
Issue Summary
When trying to move Sprints up and down the board, at times the following error is shown
Jira Software cannot swap these sprints as the data is in an inconsistent state. Please contact our Support team to get assistance.
Steps to Reproduce
- This is not consistently reproducible in all instances
- But in the affected sites, you only need to browse to the Backlog page with multiple Sprints
- Try to move the sprints up or down
Expected Results
The sprints move accordingly
Actual Results
The below error is thrown as can be seen in the HAR: Jira Software cannot swap these sprints as the data is in an inconsistent state. Please contact our Support team to get assistance.
This happens since the Sequence which has been associated with the Sprint gets duplicated in the database.
Workaround
There is a automatic production fix for the issue that does not require manual intervention from support.
This fix is now live on production (100%) as of (14 Aug 2023).
Upon detection of this issue, the fix will automatically be applied in the background and the tenant will be entirely patched shortly after (~5 seconds).
The next request to move a sprint should then succeed without any issues.
- was cloned as
-
-
- Gathering Impact
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[JRACLOUD-90735] Moving a sprint on a board at times returns an error about inconsistent state of data
Thank you Matt Ray, that fixed it for me.
Proposed steps to reproduce:
- Migrate existing sprints from self-hosted Jira to Jira cloud.
- Create several new sprints in Jira cloud.
- Move sprints up and down.
- Continue creating until the error appears.
Possible work around: as described by Matt Ray above. For me I ended up needing to delete all migrated sprints.
Was unable to move new sprints above a specific sprint (call it "BLOCKING SPRINT").
Able to get around it just now by:
- Create new sprint - let's call it NEW SPRINT
- Move all issues from BLOCKING SPRINT to NEW SPRINT
- Delete BLOCKING SPRINT
- Rename NEW SPRINT
Was able to move other sprints around after that.
This is a major issue that needs to be addressed with high priority. I keep receiving it the last 1-2 weeks and I am afraid I won't be able to start my next sprint since it cannot get first in the list
I thought this would be fixed by now, but since it's not I'll also chime in to hopefully get this issue more visibility.
Used empty sprints as well as sprints with tasks within them, same result. Initially will be able to move up a 3 spaces up before error. After renaming, can move 1 space up. Renaming again doesn't allow for moving the sprint up again. Moving the sprint above the bugged sprint 'down' also results in an error.
Haven't had an issue in the past month, I must of inadvertently closed the problem sprint without realizing it based on the work around Matt Ray described.