Use item comment for checkin comment if latter is blank

[daboy1216]

Okay, after reading through several threads, I think I understand the distinction between item comments and checkin (changeset) comments. So, here's my feature request: if I check-in a single file (either in VS.NET or Vault GUI client) and provide an item comment, but not a checkin comment, just use the item comment as the checkin comment! It really does make sense for a single-file operation. It's very confusing to our developers when we require check-in comments, but they don't appear in the Merge Branches wizard (which is an integral part of our release process). The item comments also don't appear in the History by Version window, but I'm the only one who really uses that.

I'll even go as far as to say that if the item comments are identical for a multi-file operation, apply that as the changeset comment. Again, this is all hinging on the changeset comment == "". If a changeset comment is specified explicitly, obviously use that.

[lbauer]

If a file has no item comment (on checkout), the Vault uses the changset comment as the item comment. You want this to work the other way, too -- Use the item comment for the changeset comment, provided there is just one item to check in or all items have the same comment.

I'll log this as a feature request.

[daboy1216]

You've got it.