comments required?

bwhite · Post by **bwhite** » Mon Mar 26, 2007 5:55 pm

We have "require comments" turned on.

But it is not working the way we expected.
For instance, it isn't requiring comments.

If a user enters a comment when checking out a group of files,
then when they check the files back in, they don't seem to be
required to enter a comment. *And* it doesn't use the original
comment for the group check in.

In the history view, it shows the original (check-out) comment
under the file, but under the change set, the comment is blank.

What I expect is that either a) it will require comments on check-in,
or b) it will use the check-out comment when no check-in
comment is provided.
But leaving us with no check-in comment is no good.

I prefer b), but either is better than nothing.

If this isn't clear, I can post step-by-step instructions.

Thanks,
Brad.

lbauer · Post by **lbauer** » Tue Mar 27, 2007 8:48 am

It is requiring comments (if there were no checkout/item comment, the checkin would fail), however, you'd like to see the item comment in the folder version history. I'll log a feature request for the item comment to appear in the Folder History by Version if there is only one checkout/item comment (for a group of files, for instance) an no checkin comment.

For a description on how item/change set comments work, see this:
http://support.sourcegear.com/viewtopic.php?t=4303

bwhite · Post by **bwhite** » Tue Mar 27, 2007 9:31 am

> It is requiring comments (if there were no checkout/item comment, the checkin would fail),
But not change Set Comments.

> however, you'd like to see the item comment in the folder version history.
Yes.
> I'll log a feature request for the item comment to appear in the Folder History by Version if there is only one checkout/item comment (for a group of files, for instance) an no checkin comment.
Thanks.
My personal opinion is that if comments are required, then that should aply to change set comments. Or you need finer grained options.
I would be OK with showing the check out comments in the version history if there are no check-in comments.
A better option might be, use the check-out comments as the default for the check-in comments form. You have the question of what to do if the check-out set doesn't match the check-in set. But that's true of the other solutions as well.
That's why I like the default option the best. Give the user a chance to see the comment and change it.