Finding All Locks on Members of a Sandbox or Project
|
CLI EQUIVALENT
|
si projectlocks
|
You can use the View Project Locks action to find locks by all users on all members of a sandbox or project. You can also remove all or selected member and non-member revision locks if you have RemoveOtherUserLocks permission. For example, assume that you are a configuration manager for a software release that is nearing the end of development. Before project access is restricted, you would want to find all locks to remove those on members that are no longer to be changed.
The View Project Locks action displays the Project Locks view, which shows the following information by default:
• Project—Path and name of the project from which the member revision is locked. If the member revision is locked from a shared subproject, the subproject path and name are shown.
• Development Path—Name of the development path from which the lock on the revision was made. This information is relevant when the locking policy is set to devpath. This allows a single user to have a single lock on an archive per development path.
• Member Name—Name of the locked member.
• User—User name of the person holding the lock.
• Lock Type—The type of lock obtained on checkout.
• Revision—Locked revision number.
• Time—Time that the archive was locked.
When you select a sandbox or project before running the View Project Locks action, you are asked if you want to include all subprojects. If the number of subprojects is very large, server performance can be impacted. If you need to view locks only in a particular subproject, you can select the subproject.
Once the Project Locks view displays, you can apply text filters to limit the locks that are shown. To remove locks, you right-click selected members and select Remove Lock. Your ability to remove locks on a project or subproject depends on your RemoveOtherUserLocks permission. For example, assume that you have permission on a project but no permission on a shared subproject. You are able to remove locks on members in the project but not in the shared subproject.
Finding Locks From the GUI When a Sandbox or Project is Selected
When a sandbox is selected in the My Sandboxes view or a project is selected in the Projects view, finding all locks on members is easy.
1. In either the My Sandboxes view or Projects view, do one of the following:
◦ Select the sandbox or project and select > > .
◦ Right-click the sandbox or project and select View Project Locks.
The Include all subprojects window initially opens by default. If desired, you can select Remember this answer and don’t ask me again before clicking Yes or No. Your answer is then remembered and used the next time that you view project locks. If you ever want this window to open once again, you must select > > > > . You then set Include subprojects to ?.
2. Click Yes if you want to see locks for the project and all subprojects. Or, click No if you want to see locks for only the project.
The Project Locks view displays the locks. You can then apply text filters to limit which locks are shown and remove locks.
Finding Locks From the GUI When No Sandbox or Project is Selected
When no sandbox or project is selected, you must specify the project or sandbox development path in which you want to find all locks on members.
1. Select > > . When no sandbox or project is selected, the Select a Project to view locks wizard starts and displays the Specify the mainline project page.
2. Enter or select the project in which to find locks and click Next. The Specify the mainline or variant project page appears.
3. Select the development path (optional) and click Finish.
The Project Locks view displays the locks. You can then apply text filters to limit which locks are shown and remove locks.