Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira issue edits being overwritten - how can this be prevented ?

Summary of problem:

  1. Two users are in edit mode on the same Jira issue field at the same time, both have issue version x open and are editing the same field
  2. user 1 saves a change, issue becomes “version x+1 edited by User 1”
  3. user 2 saves a change to their version of “Issue version x” which overwrites the latest saved version, “version x+1 edited by User 1”,  and becomes  “version x+1 edited by User 2”
  4. Meaning a committed field change by user 1 has been lost.
  5. In Step 3 before allowing user 2 to commit their save, Jira should be checking that the version of the issue about to be saved by user 2 is at the same version as when user 2 went into edit mode.  In this example only commit user 2 edit if original issue is still at Version x

Has anyone out there experienced this problem and how have they prevented the loss of data ? 

Thx, Rob
(Jira cloud instance) 

3 answers

1 accepted

0 votes
Answer accepted
Clark Everson Community Leader Aug 29, 2022

Many thanks @Clark Evans  - yes got the same feedback via another channel too. Looks like a known issue that just needs more votes to push it along.  In the mean time I think an improvement in the teams ways of working can help circumvent the occurrence. 

Appreciate the time you took to reply


0 votes
yuliia_b__SaaSJet_ Marketplace Partner Aug 30, 2022

Hi @Rob Crick 

It seems there is no way to prevent Jira issue from editing. But your data won`t be lost – you can always check what was updated in the issue history. If User 1 and User 2 have made some changes, it will record each of them. 

two users history in jira.png

Also, you can check the app from my team – Issue History for Jira. It's easy to monitor every team member's activity as it records everything in one report.

Log of changes.png

Thx @yuliia_b__SaaSJet_ 

Some useful help - the concern though is that the user isn't altered to the fact of a save mismatch so doesn't go looking for the history to check if a change has been effectively backed out. 



0 votes
Pramodh M Community Leader Aug 29, 2022

@Rob Crick 

The data would not be lost, it will be saved in the history section of the issue.

Did you try to explore the changelog of an Issue?

Since the screens are not dynamic meaning when you open a screen it is not in any way connected to the server, so it cannot check the two/more users making the changes at a time.

Only when the user submits the issue changes, the server is contacted and it will be able to store the changes.

Check the history & let me know


Thanks @Pramodh M , 

yes can see the history log, the working practicality is that if the user doesn't know of an edit "clash" they won't go looking into the history log to confirm the correct save order. 

So as per my reply to Clark a change in ways of working will need to be made to reduce the likely occurrence.

Rds, Rob    

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events