I don't know if this a bug or unsupported feature ;-) but the GUI let you move a work item to any other folder by drag/drop or using the context menu "Move to folder...". If you try to do so it will move the item in Outlook GUI but not on the TFS Server, given the illusion that the item has indeed been move. For a feature like "Move to Folder..." to work it must be limited to moving between projects only with some attention put on field validation regarding Area Path and other project defined values. The "Move to Folder..." would be very useful for us as most of our bugs are reported though TeamLook and it happens offend that they are created in the wrong Team Project.

Cheers
  Lars

Lars,

This is a great question, and I really wish I could answer that it is just an unsupported feature... Unfortunately, there are good technical reasons why this "just is".

TeamLook uses the default Outlook views to display the Work Item results. This gives us the great benefit of organizing the results of the query to look like an inbox. However, since we use the Outlook views, we automatically inherit the Outlook context menus. You cannot remove/edit items in the right-click context programmatically and therefore the buttons for moving items to other folders will always exist (along with the other right-click context buttons). If you refresh your query after moving an item, you will see that it always gets regenerated if it still is returned by that particular query. If you switch to the folder that you moved the item to (assuming the destination folder was a TeamLook query), the item will quietly get deleted upon refreshing. Besides just not being able to remove the context buttons, much of the functionality of the right-click context is not exposed through the Outlook API, which severely limits the ability to catch any events before they are fired.

Second, TFS items that exist in a given project cannot be moved to other projects. This really makes sense as each project has a different process template and a Bug in Project A may be a completely different type than a Bug in Project B. So trying to do a move like this wouldn't exactly work.

Cheers,
~Joe