Loading Profile...
Deadlock -one user was moving stories. the other was editing an unrelated story
1. I was moving a series of stories from the backlog to the icebox and then back to the backlog again. (that is how I move stories up or down in a column)
2. Jennifer was editing an unrelated story.
3. A deadlock was shown on her screen. Then she got an error that someone else was editing the same story that she was editing. But that was not true. No one was editing her story.
Do you have enough logs or whatever to diagnose problems like this? Let me know if you need more information.
2. Jennifer was editing an unrelated story.
3. A deadlock was shown on her screen. Then she got an error that someone else was editing the same story that she was editing. But that was not true. No one was editing her story.
Do you have enough logs or whatever to diagnose problems like this? Let me know if you need more information.
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?Thanks for reporting this Heidi, we should have enough information in the logs to follow up on this issue.
Earlier investigations of this issue uncovered two problem areas in the code. The first issue was due to some old code that was unecessarily updating the project every time a story was being updated. This caused some of the deadlock issues previously reported. That problem has been fixed and will be deployed in the next release.
The second problem area is around the way we update story priorities when a story is moved. Moving a story updates the priority of a number of stories in the same panel/"bucket". This means a user is moving a story around in a panel at the same time another user is editing a story, can cause a deadlock error. This bug has been recorded and will be prioritized for one of the upcoming releases.
Mark -
Inappropriate?Thanks for being so responsive to this! We really appreciate it. -Heidi
EMPLOYEE
