Loading Profile...
If one person is editing a story and another person moves that same story, the person editing loses their work.
1. Person A should open a story and start editing the description.
2. Person B should now move the story that Person A is editing.
3. Notice that Person A loses the work they did when editing the story, and Person B succeeds.
I was just Person B and I ticked off Person A!
Suggestion: In a case like this, don't let person B move the story. Show them this message: "The story you are trying to move is locked for editing by another user. Please try again in a few minutes."
2. Person B should now move the story that Person A is editing.
3. Notice that Person A loses the work they did when editing the story, and Person B succeeds.
I was just Person B and I ticked off Person A!
Suggestion: In a case like this, don't let person B move the story. Show them this message: "The story you are trying to move is locked for editing by another user. Please try again in a few minutes."
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
-
Inappropriate?This is an unfortunately situation when a user loses work, but locking stories for update would cause other issues. For example a user might start updating a story and then head to lunch or home. All other users would be unable to make any changes to this story until that user came back.
We have had some discussions in the past on the best way to solve this problem. One thought that had some traction was to automatically merge non-conflicting changes. This should help limit the times a user lose work. I will see if we can get that issue back into the Tracker road map.
As always thanks for the feedback! -
Inappropriate?+1 -- I've been bitten by this one more than once as well.
I'm not crazy about the locking idea, but would love to see this behavior go away. It seems that if it did a dirty read before the update, then only updated the attributes changed by the user, that it should be pretty friendly to non-colliding updates. Just a thought. -
Inappropriate?We've made some improvements to conflict handling, most non-conflicting changes to stories will allow the person editing a story to continue, and not lose their changes. One known issue is moving a story from one panel to another - that will still cause a person editing that story to lose changes, but moves within the same panel, as well as things like adding comments/labels, and non-conflicting field changes, will be handled more gracefully now. Let us know how well these changes work on your projects!
EMPLOYEE
EMPLOYEE
