Missing Change Set Comment History in Version Details View

[mikecausi]

In my Vault Pro client v11. Pick any file. Show History. Select any historical version and view Details.

The Version Details -> Change Set Comment box is empty.

However, I can see the comment (in a single line) in the previous window - History Explorer (but only to a certain point before the column space cuts it off).

This started to be an issue somewhere between an early v10 and v11 upgrade. We went through a few updates/upgrades recently. Not sure exactly when.

I tried to install the latest client but it did not help.

Thanks in advance,
Mike

[Tonya]

Hi Mike,

Thank you for reaching out. I can confirm this is a bug that has already been reported to us. It does not appear to be related to Vault 11. This issue has been logged under item #20216 (in case you want to check on the status in the future). We will consider this to be resolved in an upcoming release.

Tonya

[mikecausi]

Thanks for the update. To add some more details, my colleagues are using the same Vault client as I am and accessing the same Vault server. They have no issues with viewing the Version Details Comments as I do.

I installed the latest download (31454) over an older build. Do you think I should uninstall and re-install the client to see if that would help?

Thanks.

PS I am trying to sort this out because viewing historical comments is a very important step for me. At the moment, I am relying only on basic email notifications to search for and access the comments for the change set.

[Tonya]

Hello again,

Yes, my suggestion would be to uninstall the Vault Client and reinstall the client. I would also try clearing your client-side cache file:

Please let me know if this doesn't help.

Tonya

[mikecausi]

Thanks for the quick responses, Tonya. Unfortunately, this didn't help. I tried resetting the client cache first (all 4 options in Tools-Options-Local Files). I then uninstalled the client and reinstalled the client (same build as others have installed, 31452) and reset the client cache again. Should we update to the latest build (31454) on both the server and clients? Let me know if you have any other things to try. Thanks.