New File Version for Moved Files

[buckey]

In Vault 5.0.2, when I move a file, a new version of that file is not created (The file is simply moved). So there doesn't appear to be a way to know that this file was moved when viewing history for the file. Is there any way to force Vault to track this type of file movement in the history for the actual files? I mean, I know when working with an asp.net project that the project file will be updated (if the file movement occured in Visual Studio), but when dealing with a larger project which has multiple developers, the project file will be modified many, many times. So it becomes very (VERY) burdensome to try to backtrack through each and every project file that is stored in history in order to find when a specific file was moved from its previous location.

Does anyone know of any settings (hidden or otherwise) that will allow Vault to actually track these file movements in history?

Thanks.

[lbauer]

The history IS tracked, but at the folder level. If you Show History on the folder where the file previously existed you'll see "Moved to . . ." and the history of the folder where the file is now will show "Moved from." To find Move options, you can filter by Actions->Move in your folder history query.

There's nothing in the file history itself, since the file didn't change, just its location. I can log a feature request for moves to be tracked in file history.

when I move a file, a new version of that file is not created

Do you want to create a new version of the file? If, so you could Branch. The branch operation can be used to create a copy in another location in the tree. The file history of the branched file shows the branch operation.

[buckey]

Thank you for the reply. Viewing the history information at the folder level provides me with the information that I was looking for. I just expected it to be at the file level. Now I know...Thanks!

[lbauer]

You're welcome.