Show history incomplete

kasti · Post by **kasti** » Tue Jul 12, 2005 7:32 am

Hi,

using Beta 3: For some of our users, the show history command will only return label actions. No other actions (e.g.:checkin/out) are shown even though all actions are selected and no filters are applied.
For other users it works perfectly.

Thanks,
Herbert.

lbauer · Post by **lbauer** » Tue Jul 12, 2005 2:55 pm

Since this is machine-specific, what's the difference between the machines where history functions properly and those where it does not? Do users have different versions of the .NET Framework? Are the operating systems\service packs different?

Are they doing the identical History operation?

kasti · Post by **kasti** » Thu Jul 14, 2005 7:45 am

Hi,

Ok we did some more tests. The problem is with the user and not with the computer. On one and the same computer, one user sees the complete history, the other only labels. Rights to the project are the same for both users.
This problem has only appeared once we updated to Beta3. Before, everything was ok.

Bye,
Herbert.

lbauer · Post by **lbauer** » Thu Jul 14, 2005 7:57 am

We still have copy of your database here from a prior support case. We can try to reproduce this here. We need the following info: the name of the two users and the specific steps used for the history operation. Let us know which user saw only labels.

Also, if the rights for these users has changed since you sent your DB, let us know, otherwise we'll assume they are the same. You can email the info if you prefer.

kasti · Post by **kasti** » Thu Jul 28, 2005 6:21 am

Hi,

Found out that it depends on the default user rights. If you switch them off, then only labels are shown in the history.

So, if you want to test yourself, upgrade the DB to vault 3.1 (3476) - I think it was Beta 3. Then look at a user:

e.g.: mdruml

No checkin history is seen, but if default user rights are changed, then everything is ok.

Bye,
Herbert.

lbauer · Post by **lbauer** » Thu Jul 28, 2005 12:25 pm

We sent Herbert a new stored procedure for the Vault database and that appears to have fixed the problem.

This fix will be incorporated in Vault 3.1.1, due out soon.