Vault 2.0.6 History Export Bug - Where's the path?

montek · Post by **montek** » Tue Jan 04, 2005 8:50 am

I just upgraded from 2.0.1 to 2.0.6 to fix a bug per Jeff and the history exports no longer include the full path to the file.

This is a critical bug for us because our developers must include deploy lists with their tickets, so we can schedule them for testing and deployment to our production system.

Help!!

lbauer · Post by **lbauer** » Tue Jan 04, 2005 1:25 pm

This was an issue with Vault 2.0.6, but has been fixed in Vault 3.0. I've also responded with some suggestions to your email to Tech Support.

mlippert · Post by **mlippert** » Wed Mar 02, 2005 1:52 pm

I'm not sure exactly what is meant by history export, but I am running Vault 3.0.2 and when I get the history of a folder by version(changeset) and then view the details of a changeset the files modified as part of this changeset lists only the filename and not the path (Vault path) to the file. This is not helpful, as for example in one changeset I looked at there were 8 file's named "makefile".

Also while I'm talking about the changeset details page, I really want to be able to get to the individual file's history, so I can do a diff to see what exactly was changed for this version of the file in this changeset.

Mike

Post by **jclausius** » Wed Mar 02, 2005 1:56 pm

Mike:

Full item path within the change set details ( as well as diffing from change set details ) is not in the current release ( Vault 3.0.4), but this feature is scheduled to be released in Vault 3.1

mlippert · Post by **mlippert** » Wed Mar 02, 2005 3:03 pm

Thanks. Glad to hear it's on a planned feature set for an upcoming release.

That is the best possible response I could hope for!

Mike

montek · Post by **montek** » Wed Mar 02, 2005 4:10 pm

Jeff's good like that.

Post by **jclausius** » Wed Mar 02, 2005 4:37 pm

Monte - you're too kind