Unfortunately, we have had a number of cases where JIRA users have updated issues simultaneously (the last update "won" and unfortunately deleted/skipped the previous update made by another user).
Is there a simple and reasonable solution (possibly an add-on) to fix this unfortunate situation?
Thanks in advance.
This is the nature of web based tools, that they always have a kind of snapshot of the DB delivered to the browser. In your case at least the nearly simultaneous changes should be seen in the history of that issue.
One chance to reduce this is tu use something like jquery that can have a kind of open channel to the server. But imagine thousands of users - this would cause a massive network usage that would result in slowing down the response time of the server.
My advice - think about eliminating the reason for this simultaneous changes. Or advice the users to update their view of the issue first, before they plan to edit.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events