Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to avoid story modifications being overwritten between UI refreshes?

Chris Kimball
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 17, 2020

We have experienced a phenomena in Jira Cloud that can be reproduced as follows:

Step 1. User 1 makes an update to a story description and clicks “Save”
Step 2. User 2 makes an update to the same story description before the UI refreshes and clicks “Save”
Step 3. User 1 refreshes their screen
Step 4. User 1 sees User 2’s updates in the description, but not User 1’s updates in the description
Step 5. Both updates are visible in the story History

If Steps 1-3 occur before a refresh of the UI occurs, then Steps 4 and 5 apply. I'm making an assumption that there is some kind of write action happening between the Application layer and the Session layer since both User 1 and 2's updates are visible in the history... but that something is happening with the refresh of the Presentation layer before the Session layer can tell the Application layer that there was an update... WHEW! Anyone know a way around this?

1 answer

1 accepted

0 votes
Answer accepted
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 20, 2020

Hello @Chris Kimball

Welcome to the Atlassian Community!

Indeed, Jira does not provide a way to handle the issue updates of two or more persons at the exact same time and implement both while one of the changes is rendered, causing one of the updates to be overwritten in the issue.

We have three feature requests to provide some alternatives that would improve this behavior here:

Notify user when editing a story will overwrite another user's changes 

Implement issue locking 

Sync issue updates simultaneously 

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

As a workaround while we work on the implementation of those feature requests, there is an App that can help you identify the persons that are currently viewing the issue and avoid or be aware of this problem possibility:

Who's Looking for Jira Cloud 

Let us know if you have any questions.

Chris Kimball
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 20, 2020

Thanks for the quick response! I voted for "Sync issue updates simultaneously". I think that solves the problem in the least invasive way to the end-user. Thanks!

Adrienne Lalla November 5, 2021

@Petter Gonçalves   i have also experienced this and on top of that there have been instances where I could've sworn I updated a story but my update disappears and does not show in history.  I am not sure if it's due to multiple people editing or windows open at the same time etc.. has this also been noted (asking so I don't feel like I'm going insane haha)?  There is one other person at my company that has experienced this but everyone else seems to have not come across it.

 

Is there a roadmap for the above 3 issue fixes/updates?  Thank you!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events