Feature to add - Exclude Option in History Explorer

[roman]

Hi guys,

There is a very annoying feature of History explorer - showing a lot of lines with:
Added ~ and Deleted ~ files with the comment "Temporary file created by Visual Studio .NET ..."

I know it was complained about this issue in 2004 and the issue was brussed aside by SG rep saying that nothing can be done about it.

Well, there is a very easy fix - just need to add an option (preferably multiple options) to EXCLUDE history entries based on the comment column text. Actually some other tabs could use this option as well.

Adding this feature would make life of all of us that have to go through history and verify the changes much easier.

Second request: in addition to the above, a text based report like VSS provides would be really welcome. You are trying to replace VSS, but this is one feature that would be really handy for team leaders. It allows to see at a glance what a particular developer added, deleted, modified, etc. NI is usinf Vault for 1.5 years now, and I always miss this feature of VSS.

[mskrobul]

Well, there is a very easy fix - just need to add an option (preferably multiple options) to EXCLUDE history entries based on the comment column text. Actually some other tabs could use this option as well.

I will add this as a feature request. We have had some other requests for history query excludes (like exclude users, for example).

Second request: in addition to the above, a text based report like VSS provides would be really welcome. You are trying to replace VSS, but this is one feature that would be really handy for team leaders. It allows to see at a glance what a particular developer added, deleted, modified, etc. NI is usinf Vault for 1.5 years now, and I always miss this feature of VSS.

You can currently save your history query results as an html file, or comma separated list or a tab separated list (from history explorer choose File->Save Results As). Do you want to save history in a different format than one of these?

[roman]

As far as I could see you can save only the list entries in comma delimited or html format without the specifics of the changes. So all I know is that a specific user was working in some way on the file, but to find what he did, I have to launch a diff dialog for every modified file. Unless I don't see how to do it, what I mean is the feature of showing the actual changes line by line, additions and deletions in annotated format. It should be done for all files that were changed by specific user(s) on the selected date(s). So Vault history analysis would show the old and new line numbers of the code with the changes in a document format (see old VSS history report).

Roman

[mskrobul]

I will log a feature request to optionally include file differences in a history report.

For now, Vault Web may help your team leaders easily see what has changed in Vault. You can view recent checkins for each repository from Vault Web, view blame (which will show the files with the changed changed lines highlighted along with the version number for the change was changed and who made the change), view differences and view history.

[jclausius]

One other note on Blame for the developers in the trenches. Blame can also be launced from within the Vault GUI client. From the menu View -> Show Blame. A cool feature of Vault which on a number of occasions has helped track down who requires flogging with a wet noodle.

[roman]

Hi Jeff and Mary,

Thank you for placing the features on the development list. I just want to say that yes, blame is a good step in the right direction, but it allows to view only one file, and also it does not have an option to see only a selected user changes/edits. Just making sure that you know that blame does not get you off the hook

[HogOfTheHills]

Any thoughts/progress on adding an option to include file differences in a history report similar to what's available in VSS?

It would be great to be able to export such a report to xml, so that one could apply a custom xslt for display/processing. Including a default xslt to match what VSS currently does would be a great start.

[Beth]

This feature hasn't been added yet, but it is still logged. I will add your "vote" to that feature and your additional suggestion. Thanks for the feedback.

F: 10331