We recommend using Visual Studio 2017
This documentation is archived and is not being maintained.

How to: View Pending Changes in Other Workspaces

Source Control Explorer lets you view and manage pending changes in your workspace and also to pending changes in other workspaces. Therefore, you can easily see whether other team members have pending check-ins. The following procedure demonstrates how to view pending check-ins that have been submitted in other workspaces. For more information about viewing and managing pending changes in your own workspace, see How to: View and Manage All Pending Changes in Your Workspace.

Required Permissions

To perform these procedures, you must have the Read permission set to Allow. For more information, see Team Foundation Server Permissions.

To view pending changes in other workspaces

  1. On the View menu, click Other Windows, and then click Source Control Explorer.

  2. In Source Control Explorer, the Pending Change column identifies all pending changes that are ready to be checked in to Team Foundation version control. There are three ways in which pending changes will be reflected:

    • If only you have a pending change, the Pending Change column will indicate the pending change type with your name or alias in the User column.

    • If one other team member has a pending change, the Pending Change column will indicate the pending change type with their name or alias in the User column.

    • If two or more team members, which can include yourself, have pending changes, the first user to submit a pending change will appear in the User column together with an ellipses (). To view a list of users and pending changes, follow these steps:

    1. Right-click the item in the Name column and click Properties.

    2. In the Properties dialog box, click the Status tab; notice the listing of users in the User column and their associated pending changes in the Change Type column.


    You can also see all pending changes in all workspaces using the tf status command. For more information, see Status Command.