Locking bugs temporarily?

[Gervase Markham]

Hi Max,

Thanks for taking the time - I know you are busy :-)

On 26/02/12 04:50, Max Kanat-Alexander wrote:
> 	My original plan for the API on this was to allow people to pass a
> parameter to Bug.update, perhaps "check_conflicts => (time)", which
> would then return an error if there had been changes since the specified
> time. The error would include the changes that had been made, in enough
> detail that an external app could re-create the "mid-air collision" page
> that Bugzilla currently has in its UI.

At the moment, if you pass a modification_time, the BzAPI will do
collision checking and return an error if there's a collision. (It's up
to the client to get a new copy of the bug, figure out how to merge the
changes, perhaps with user assistance, and resubmit the request.) If you
don't pass a modification_time, it does an unconditional overwrite.

However, this doesn't solve the problem - my extension does not have the
ability to talk to a "user" to resolve any mid-airs. Therefore, the
mid-air needs to appear on the screen of the _other_ guy trying to
change the bug - the real person. That means, I need to have a "lock" or
something on the bug while I'm changing it, so that when the lock is
released, _their_ change fails. I don't want users normally using the
web interface to get a lock, only to respect my lock! :-))

Any thoughts on how to do that?

Gerv
_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla