>>>Suppose you need to track the changes done some days ago, what do you do? restore the backup ov every day and compare? Could be very time costly. With Source Control (any tool, even old SourceSafe is better than no Source Control!) you just select a point in time and Diff, then go back to previous changeset and Diff...
>>
>>And supposing you trained your developers (and yourself) to leave a meaningful comment when checking in, a brief description of what was done and where, this can be even faster.
>
>Or a link to the OnTime (or similar product) feature or defect or task that contains that information. Vault and others have this capability.

For this team it was lost after a while, one of the upgrades has removed the entry from the setup or the link needed to be created differently. But it was working the wrong way - if you entered the FogBugz number in the bug# field on checkin, it would show the checked in files when you looked at the bug. It would be much better if it popped the bug text in a tooltip, or contained a link to it, when you look at the history of a file in Vault.

I find it much more useful to know what happened to a file, because I'm just about to open it and I want to know what was changed in it and whether that's relevant (or at least related) to what I want to do. To look at an old bug and see which files were checked in when it was solved is gold plating - nobody really looks at old bugs, unless they are ancestors of new ones (which happens once a year... not every year).