"Commit selected" removed from context menu

[jclausius]

Yes. Nothing has changed since my last post.

[jclausius]

An update for this feature in Vault 5.1.2 on the Vault Dev blog - http://vaultblog.sourcegear.com

[jclausius]

The Vault Standard and Vault Professional 5.1.2 address this issue.

[davenovak]

Much appreciated.

Is it possible to use this newest Vault client with 5.1.1.19215 Vault server? I ask because I'm interested in just seeing this change on my machine prior to "officially" upgrading to the latest version.

Please inform.

Thanks,

--Dave Novak

[Beth]

The Vault 5.1.2 client should be able to connect to a Vault 5.1.1 server. The change should be a client-side change, so you should see it with just a Vault 5.1.2 client.

[davenovak]

Just to let you know, the change looks perfect! I like having the option to use check-boxes for selection but always having right-mouse context support for Commit.

Thanks for fixing this!

[kiwirob]

Perfect? Sorry I don't agree...

At first I didn't like the checkboxes, but after a while I found them very useful.

When doing a final review of all code changes I could use the checkboxes to mark those files I had checked independently of the selected rows in the pending change set.

We have just upgraded from 5.1.1 to 5.1.2 - specifically to remove the checkboxes for some developers.

Some of our developers don't use the checkboxes and can now turn them off - great!

Some of us want to use the checkboxe behaviour as in 5.1.1 but now in 5.1.2 everytime you select a row the checkbox gets checked/unchecked automatically - this is just horrible.

Please revert the behaviour for checkboxes as introduced in 5.1.1...

[lbauer]

Before we'd consider changing this, we could use more information about how you use the difference in selecting the row or checking the checkbox.

[davenovak]

I'm mainly just happy that "Commit selected" is back on the context menu.

It might be worth noting that if you click just over the checkbox column, your previous selection remains checked, therefore allowing independent selection of rows. You can also append to your current selection by holding down the Ctrl key and clicking anywhere on the row.

[kiwirob]

I also like 'Commit selected' being back.

My issue is with the revised 5.1.2 checkbox behaviour.

Consider this workflow which could be achieved in 5.1.1 but not 5.1.2.

• I have checked out and modified a large number of files.
• As a final review before commit I want to compare the changes made in each appropriate file. This may also involve discarding individual files where changes are insignificant.
• I start at the top of the pending change set and view the differences of the first file
• If I am happy with the changes I check the file, this allows me to see which files I have reviewed
• I then move onto another modified file, select it and view the differences. In 5.1.2 selecting another file now removes the checks from every other file!!!!!

I have reverted back to 5.1.1 in the meantime.

[davenovak]

I would agree that, for this type of workflow, the new way of auto-selecting check boxes is no good at all. I'm really not sure why they've decided to go with this "auto-check on selection" method, especially when selecting any place other than the checkbox column results in all other checks getting removed. This hasn't been an issue for me as I guess I've gotten used to clicking on the checkbox column.

Another "trick" worth mentioning is that I often just do a Select All from the Pending tab, hit Commit, and from the Commit dialog go through the exact process that you describe. You can very easily (and intuitively) check and uncheck items for this commit operation there, as well as do diffs.

[lbauer]

Thanks for your comments and clarifications.

I've logged work item 16114 for this functionality. It will be evaluated for an upcoming release of Vault.