Possibility of indivisible access to JIRA issues (lock when updated)?

Question

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.

Mikhail_Kopylov · Answer

Actually this is JIRA feature. You're able to see all the changes in issue history. And roll back mistakenly hidden changes

To avoid such artifacts optimistic locking algorythm may be used.

I don't think it can be implemented in JIRA with a plugin.

Sebastian Kleinholz · Answer

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.