Vault / FogBugz integration problems

[MarcusB]

Will the Vault/FogBugz integration be improved in Version 3?

The current verison has some problems, such as:
1. Very, very slow. _Especially_ pulling up diffs
2. Have to login very often
3. Crashes from time to time, mostly when you first log in.
a. We get the "Object moved to HERE" message
b. Then we log in
c. Then we get the error:

Unable to display history items.

Error: FailObjPathInvalid

Thanks,
Marcus

[mskrobul]

Hi Marcus,

We have made a few improvements to Vault Web for 3.0.

1. Very, very slow. _Especially_ pulling up diffs

We have greatly improved the speed of Diffs in Vault Web for 3.0.

2. Have to login very often

There isn't much we can do about this since Vault and Fogbugz are seperate applications. If you logout or close down the Vault Web browser, you will need to re-login.

3. Crashes from time to time, mostly when you first log in.
a. We get the "Object moved to HERE" message

We made a change that we *think* fixed the "Object moved to HERE" message. We haven't seen this behavoir since that change, so hopefully that change will fix your "Object moved to HERE" issue also.

b. Then we log in
c. Then we get the error:

Unable to display history items.

Error: FailObjPathInvalid

Have the files in Vault been moved or been renamed that you are trying to view? Fogbugz sends us the path to the item in Vault, but that path is the path to the file at the time of checkin. If that path has changed (file renamed, moved etc), Vault Web will not be able to find the file.

[MarcusB]

Could you use a cookie to identify the user?

[mskrobul]

We do use cookies to verify that a user is authenticated during a Vault Web session.

For security reasons (since it is possible to view code from the Vault Tree through Vault Web), when the Vault Web session ends (the user logs out, session times out, browsers are closed) Vault Web requires the user to re-autenticate.

Are you getting promted to re-login when the Vault Web session hasn't ended?