I have configured my vault repository to require a bug id, and the Visual Studio plugin promptly asks for this bug id when I try to check in, but there's a problem.
Just now, I had 10-15 files waiting to be checked in to mark the completion of a rather nasty bug which involved rewriting and adding little bits and things in a lot of classes.
I type in a comment describing the fixed things, and click Check In and I get the dialog. But, I don't remember the bug id so I hit cancel. And... the list of pending checkins gets shorter.....
All the files that were new (I added 2 new enums and a class) were checked in without the bug id, all files that were already in the repository and were thus checked out are still checked out.
So, there seems to be a bug, at least in the visual studio plugin, in that new files are checked in without requiring the bug id.
Additionally, I've noticed before that when I go to the bug tracking system (fogbugz), then sometimes (could be always, but haven't checked in detail) new files I checked in as part of a bug are not listed in the list of files that were checked in for that bug.
Basically, there seems to be a bug regarding checking in new files from the visual studio plugin in that they neither require a bug id to be checked in, and that they don't get reported to the bug tracking system.
I can think of one plausible reason for this. The plugin starts to check in files, then when it hits the first file already in the repository it is informed that the files need a bug id, asks me, and I hit cancel, which commits the files already checked in and aborts the checkin process.
Something to check out before your impending 4.0 release anyway.
If you need me to test something, please let me know either here or on my email lasse@vkarlsen.no
Regards,
Lasse Vågsæther Karlsen
Vault sometimes allows checking in without bug id
Moderator: SourceGear