Certain changes can be overridden

Nikki Parker

In the last 2 releases we have done, issues that were moved from one release to another were reverted back.  We think this was done while an admin user changed the release version of an issue while another user was editing the status of the issue.  The admin user had moved an issue from release "x" to release "y" and afterward, the issue was back in release "x"

Steps to Reproduce:

One user logs in and is editing an issue

One user (an admin) logs in to their dashboard and moves the issue from release "x" to "y" & saves

First user finishes editing and clicks save

Looking at the issue or the release list(s), both users see the issue is back in release "x" and it shows in the history of the issue as having been changed by the user who was editing the issue.

Presuming this is a known issue, is there a fix in place or forthcoming?

Andy Heinzer

Hi Nikki,

As I understand you have found that when two users try to edit an issue in Jira Cloud at the same time, the user that saves their changes last wins, so to speak. 

This has always been possible within Jira, because Jira does not have a means to lock issues to only let them be changed by the user viewing the issue at that time.  Any user with permissions to, could make changes to an issue at any time.  There is an existing feature request for such a feature in JRACLOUD-6146 : Implement issue locking. Although this request has been around for a long time, to the best of my knowledge there is not currently plans to implement such a feature.

Several users have encountered this same problem in the past. The description on that ticket does suggest the use of some 3rd party add-ons that could help work-around this problem by trying to prevent simultaneous edits, such as Who's looking for Jira Cloud or Issue Lock for Jira (who's editing) for Jira Server.  Such add-ons might not help for situations where changes are made on a board, but for users viewing an issue it can certainly help to give insights into who else might currently be viewing an issue before making changes to it.

Sorry there is not a better solution to this right now for Jira Cloud.  But I would suggest voting on that issue as this can help our team plan on which features to implement for Jira in the future.

Regards,

Andy