While using Integrity it will sometimes happen that a user likes to lock a member which already have an exclusive lock from another user.
Today the first user have either the possibility to also lock same member revision, and then to talk with the other user when he will be ready with it's change,
OR to look on a regular basis when he will release his lock either by check-in or with "remove my lock". (=> Lock removed => everything is ok, first user have his lock.)
After the check-in it is possible that between the CI and the time the first user get's knowledge of it, another user has done an exclusive lock on the member's new revision.
The first user has again the same problem like described in the first two sentences of this entry.
My suggestion for the RfC is the following:
If one user have an exclusive lock on one member, and a second requests also an exclusive lock, then the "Check-in" or "Remove my lock" of the first user should have the following effect:
the lock of the second user should be moved onto the new member's revision, and the second user should be notified within his Integrity client (new info icon in the menu bar) that he has got the requested exclusive lock.
Advantage of such a function:
The user who wants to have the lock does not have to search whether locks has got released (maybe several times, might be combined with the need to contact other user's that they shall release their locks), but only initiates a lock request and will get the requested locks (on new member revision for check in's OR on existing member revision if other user only removed his lock) as soon other users are ready.