Yet another enhancement request... I just had a mid air collision with someone editing the same bug at the same time. While that was moderately fun (!), it should not have been possible. One way around this problem is to put a hidden field on the bug update form, containing the last modification date of the bug. When a bug change is submitted, it should then be refused if this field does not match the last change date in the database *at submission time*. That way, if someone edits the bug I am editing, and submits before me, I do not overwrite their changes. Instead, I get to read what the other person has written before submitting my changes. This should be reasonably easy to implement.
Priority: P3 → P1
Whiteboard: suggestion for how to fix the problem included
The bug in question, BTW, was bug 5146.
Wow. This strikes me as a really really good idea. Thanks!
Status: ASSIGNED → RESOLVED
Last Resolved: 20 years ago
Resolution: --- → FIXED
OK, done. You can still theoretically get into problems if someone is using the "make a changes to a bunch of bugs at once" feature. However, those kinds of collisions tend to be much less nasty anyway (because when changing multiple bugs, it knows to only pay attention to the fields you select, but when changing a single bug, it tends to stomp on all the fields).
Severity: enhancement → trivial
Status: RESOLVED → REOPENED
Whiteboard: suggestion for how to fix the problem included → problem still occurs
This bug is being reopened because I just submitted two entries to bugzilla on this bug and this one (sent after the first) got through.
Status: REOPENED → RESOLVED
Last Resolved: 20 years ago → 20 years ago
Severity: trivial → enhancement
Status: RESOLVED → VERIFIED
Whiteboard: problem still occurs
Hey! Wow! It worked! Only one of my modifications made it! (Sure, it was the second one I sent, but there are many factors involved and it just happens that the wrong one was the one to get through...). I love the "Mid-air collision detected!" page, by the way. Excellent.
Thanks! I was pretty happy with the way it turned out. Too bad people won't usually see all that hard work. :-)
Moving to Bugzilla product
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
QA Contact: matty
Target Milestone: --- → Bugzilla old
Version: other → unspecified
You need to log in before you can comment on or make changes to this bug.