Inconsistent Move

[scaiferw]

We had an unusual situation recently that I would like to investigate.

A QA user moved a subfolder from the development folder - to which she has R permissions - to the QA Work in Progress folder, for which she has RCA permissions.

For her, the package was gone from the source folder and appeared in the destination folder. She encountered a Checkout Failed error when she checked the material out.

Other users could not see the moved material in the destination folder - it remained in the original folder in their view of the file tree.

I have two questions:

1. Is this known behaviour? Am I missing something?

2. Is there a way to prevent users from moving, or even appearing to be able to move, material from a folder to which they have only Read permissions.

[lbauer]

This is expected behavior (though perhaps not very intuitive).

In the Vault GUI Client, you can delete, rename, move, and edit items in the tree, but wait to commit these items to the repository by turning off auto-commit (Tools->Options->Concurrent Development Style). This is useful for testing things on the client machine before checking in.

When auto-commit is off, the transactions are kept in the Pending Change Set until the user is ready to commit or check them in. In the user's Vault Client, it looks like the transactions have happened. But these are only local changes and can be undone by right-clicking on the items in the Pending Change Set and selecting "Undo . . ."

Note that when your user tries to Commit or checkin the Move, it fails, because she does not have rights to move the item. The failed transaction is still sitting in the pending change set, so it appears in her view of the tree that the folder is no longer in its original location.

The reason the other users don't see her changes is because they are not in the repository yet.

[scaiferw]

In this case the user had Tools > Options > Check In / Branch > Auto-commit after each operation checked.

Any idea why she would have seen this behaviour with that checked?

[lbauer]

It still will fail if this is checked, it's just that it will fail right away, and the Move operation will still be in the pending change set.

From you post it wasn't clear if the user did the move and then later tried to check it in. That's why I though auto-commits were off.

[scaiferw]

Gotcha.

Perhaps a feature request that moves without required permissions be refused up front so the user is aware.

I presume that the problem here is that the user doesn't have permission for the 'delete' side of the move.

Thanks,

Rob

[lbauer]

Perhaps a feature request that moves without required permissions be refused up front so the user is aware

Yes that's a good idea.

A user with Read-only access can Get files, View files, etc, but cannot make any changes to files/folders or to the repository structure. That's why the move is failing -- it would change the folder tree. in the node where she has no rights.