Prevent exclusive checkout on mergeable files

[ThomasC]

Some months ago when Vault 4.0 was first released I asked whether it would be possible to prevent users from checking out mergeable files exclusively. As I read the most current documentation on Vault 4.1, it still does not appear that this restriction has been created.

Am I correct in stating that in Vault 4.1 you cannot prevent users from checking out mergeable files exclusively? The reason this feature is so important is so that a manager can impose an Edit-Merge style development style and prevent developers from accidentally or accidentally-on-purpose ignoring this mandate and then going on vacation.

[lbauer]

Users can check out files exclusively in 4.1 as well. The Vault admin can undo checkout of files in the Vault admin client in Source Code Repositories->RepositoryName->UndoCheckout.

[mshe]

I second this idea - I've been looking for this feature since v3.0 of Vault.

While undo checkout in the admin tool works, it leaves the developer who checked out the file with a renegade. It would be nice to enforce CVS style development without resorting to admin undos

[lbauer]

I'll add this as a feature request -- the ability for Admin to turn off Exclusive locks.

[Chiramisu]

I know this is a very old thread, but here we are on version 6.1 and this feature still has not been added.

I would like to reiterate this request. It gets tiresome having to constantly unlock files that people forget to check-in, or they have not taken the time to configure their concurrent development settings to the CVS Style. This, by the way, should also be an option; i.e. Admin ability to configure the default for this setting. As the client must connect to the server anyway, I see no reason why the server could not push this configuration out to the clients.

Regards,
Matthew

[lbauer]

Thanks for your additional comments. I'll add them to the feature request.