Find local disk sandbox associated with repository workspace

why is it useful?  currently if a developer has many repository workspaces say 10 repository workspaces  then overtime the developer may forgot where the local sandbox loaded location is located on disk for each of the 10 repository workspaces. Although you can see a  list of Sandboxes in the Preferences, but you cannot determine which repository workspaces are using which sandbox location on local disk. This then causes confusion and waste of development time trying to figure out where the local sandbox path of each  of the 10 repository workspaces are.

Based on feedback from hundreds of customer developers, the current implementation is problematic for developer to find there repository workspace sandbox location is located.

who would benefit? developer

how should it work? each repository workspace should make a record where the physical local disk sandbox is located (at time launch and load operation) so that when you right-click on any any repository workspace then under properties it shows sandbox disk location . For example under preference setting the following information should be reported clearly to better informed end users:

respostory_workspace_1 is loaded = B:\EWM_Workspaces\respostory_workspace_1

respostory_workspace_2  is loaded= B:\EWM_Workspaces\respostory_workspace_2

respostory_workspace_3 is loaded= B:\EWM_Workspaces\respostory_workspace_3

respostory_workspace_4 is loaded= B:\EWM_Workspaces\respostory_workspace_4

respostory_workspace_5 is loaded= B:\EWM_Workspaces\respostory_workspace_5

respostory_workspace_6 is not loaded= N/A

respostory_workspace_7 = B:\EWM_Workspaces\respostory_workspace_7

respostory_workspace_8 is not loaded  =  N/A

respostory_workspace_9 = B:\EWM_Workspaces\respostory_workspace_9

respostory_workspace_10 is not loaded = N/A