Improvement request: fetch latest content version when editing tickets

[Paddy Duke]

I'm really not sure if this is the right place to post this, but on the chance it's seen by someone on the Jira team, here goes.

To reproduce the problem this request would solve:

1. you have a ticket open in your browser (you don’t need to be in edit mode)
2. someone else edits and saves the same ticket
3. any amount of time passes
4. you edit the ticket that was already open in your browser without refreshing the page
5. your editor will contain only the content that was there when you first opened the ticket, and not any changes that have been made since
6. when you save, it will overwrite any changes made since you first opened the ticket

We just had this happen with a very large ticket. One user had opened the ticket in their browser for an earlier planning meeting and left it open, but not in edit mode. In the meantime, several others had made lots of additions to the ticket. Not realising this, the first user then edited the ticket they already had open, which effectively deleted the other user's additions, removing several hours of work.

We tried to use the history to restore the changes, but the content was mostly in tables, so very difficult to parse in the changelog, and also long enough that most of the new stuff was truncated and missing anyway.

We're now piecing it back together from memory, which is a bit painful.

It would be great if the editor fetched the latest content when you started editing, or at least warned you about edits made since you opened the ticket.

[Crystelle S]

I would log this at support.atlassian.com, there's a much better chance that someone on the Product team will see and respond.