148895 - Record "locking" oddities when updating reports

Status: RESOLVED DUPLICATE of bug 107306

(Bugzilla :: Creating/Changing Bugs, defect)

Description

[Trevor Jenkins]

Several times now I've had Bugzilla inform me other people have simultaneously
modified the same record with me. The course of actions offered are to ignore
the previous person's entry (i.e. drop it from the record)  or drop mine. Why
would I want to drop my own? This just happened as I entered an update however
when I checked the (complete) record both changes had been committed. Either
Bugzilla is reportng spurious errors or there are conditions when an transient
error has occured because of record locks. If there are occasions where these
transient errors can occur then some random back-off period should elapse and
the second updated repeated automatically. The resolution of such versioning
issues should not be left to the whim of the second user.

Comment 1

[Bradley Baetz (:bbaetz)]

The midair collisions happen because sometimes you may want to change your
comment based on what someone else says. Also, bugzilla can't resolve all
conflicts - what if you change the priority to P2, but someone else changes it
to P1 at the same time? It can't be both, so you're warned about it.

There are bugs on making bugzilla attempt to resolve things like cclists,
though, without overwriting.

Comment 2

[Matthew Tuck [:CodeMachine]]

This is not about record locking, Bugzilla doesn't lock records when you have a
bug open.  And that's why it needs to check if it's been modified since you
opened the bug.

You would want to drop your changes if someone else has already made similar
changes in the mean time, which is half of the point of this feature.

It would be nice if you could just apply your changes over the top of the other
users' if they are independent, but that is difficult technically, so it only
presents an option to overwrite their changes currently.

Bug #107306 is probably the sort of thing you're looking for.

Oh, and when I originally submitted this comment, I got a midair collision with
bbaetz, and I then changed the comment, which proves the worth of this feature.

Comment 3

[Shane H. W. Travis]

I concur with bbaetz and MattyT -- what this user seems to be after is some 
intelligent resolution to the mid-air collision problem, which is the purview 
of bug 107306. Duping this bug to that one.

*** This bug has been marked as a duplicate of 107306 ***