trying to save a modified-elsewhere ticket loses new data
|Reported by:||Owned by:||Christian Boos|
|Cc:||bboisvert@…, gay@…, thom.pischke@…, jpwasp@…, dkg-debian.org@…||Branch:|
I spent a while adding a new comment to a ticket, but when I clicked "submit" I got a page informing me that the ticket had since been updated, and I'd have to reload it and re-enter my changes. Sure enough, because trac sends pages as no-cache, the browser had tossed out my changes when I pressed the back-arrow.
I marked the severity up on this ticket because I see a loss of data as a pretty serious problem. It wouldn't even be so bad if trac had merely presented my data to me so I could copy-paste it back. An optimal solution would be trac returning me to the newly-updated ticket page with a big error message telling me that the save failed because someone else updated the ticket, and then ALSO auto-fill my changes into the appropriate boxes so I could verify and then just hit the save button again. No data loss, easy path to the most-oft-desired output.