Roadmap for Vault

[rsboe]

Now that version 6 is out, could somebody update me on what the plan is for this product?

It's difficult to avoid the conclusion that Vault is becoming the poor relation within SourceGear, with Veracity getting a lot more love and attention. That's not to say that SourceGear are going to abandon Vault users, but it would be reassuring to hear what the future plans are.

(Am I alone in wishing that Source Control tools had better reporting options, for example? Which are the most changed files in the repository over a given time period? Who's done the most checkins? Which files haven't changed in years? Even some pointers in how we could write such reports ourselves by querying the SQL Database would be welcome.)

Personally I'm a bit disappointed by the UI of Vault 6 - having just switched from SourceOffSite 5.5 which had a really attractive, flexible interface, Vault 6 feels like a step back to the GUIs of 10 years ago - and it surely wouldn't take that long to give it a visual overhaul.

Any comments appreciated.

Richard

[Beth]

I don't have the exact feature list for the next version of Vault yet, but I do know Vault is still a signature product for SourceGear. We will be discussing the next release, but in the meantime we'd like feedback from customers on Vault 6.0, both the features users do like and what they don't like.

On the reporting, you'll find that there's a couple different ways to do that before going to SQL queries. Some can get the results they want with finely tuned history queries. Some others will perform history queries, save those history queries as .csv files, import those into Excel, and then manipulate the results in Excel. For really complex reporting, you might want to next consider using either the command-line client and then parsing the results to get what you want out of it, or you can use our Client API to create your own little report creator.

Let's start with your highest priority report and I'll try to give you some examples of how to come up with that data. What do you want to start with?

On the UI, I have a feature request that I can add your "vote" to.

F: 15175

[rsboe]

The reports I run most often using my old VSS database is:

For a given project, for a given time period, broken down by week or by month, how many:

- Individual checkins/checkouts have there been?
- how many lines of code have changed or been added/deleted, ideally by extension type
- how are the above broken down by user

I can supply screenshots of the kind of thing from a rather long in the tooth though still useful VSS addin called Code Metrics from Smart Bear (though I did send them previously to John O'Neill, who I understand is no longer with you)

Thanks
Richard

[Beth]

Here's some ideas that may help.

With Vault 6.0 what you might consider is using our new notifications systems and an email digest to give you a list of all the check outs and check ins.

You can also perform a History query, but on the Actions tab on the filter window that comes up first, select only the check in option. There isn't an option to get a list of check outs, because those are not recorded in the history, but all the check ins will be there. After you click OK and get the results, you can go to Query - Save Results As and save them as a .csv file. A .csv file can be pulled into Excel or some other program and manipulated into a report.

On the lines of code changed, I'll post a separate post on that when I come up with something.

The username should be included in the first history query, so you'll be able to sort by user.