Locking and unlocking test artifacts

If you have the appropriate role-based permission, you can lock and unlock a test artifact by clicking its Lock icon.

1. Enable locking and unlocking for the user role in the project configuration.
   1. Click the Administration () icon in the banner and select Manage This Project Area.
   2. Click Permissions.
   3. Click Team Configuration.
   4. Under Details, select a particular Role, such as Test Team Member.
   5. Under Permitted Actions, expand Quality Management and scroll to Save Test Case (or any other test artifact type).
      Note: Explicitly enable or disable locking for each artifact type.
   6. Verify that Lock and Unlock are enabled, as shown in the following figure:
      
   7. Click Save.

      When you lock a test artifact the state of its associated artifacts does not change. You can continue to edit the associated artifact of the locked test artifact.

      For example: If a test plan is linked to a test case and you lock the test plan as read only, you can continue to delete or edit its associated test case.
2. Open any test artifact type for which your role allows either locking or unlocking or both.
3. Click the Lock icon () in the corner of the test artifact to lock or unlock the test artifact.
   Note: The Lock icon appears only if locking has been enabled for that test artifact type.

   Depending on how your project is configured, you might be required to sign this action electronically by providing your password and a comment. When the test artifact is locked, the editable fields are disabled for editing.

4. If Electronic Signature is required, type your password and a comment about locking or unlocking the test artifact. Click OK.
5. To unlock the test artifact, click the Lock icon () again.

   In the test case editor, in the Edit Test Scripts Inline section, an option is available to automatically keep the test script's state and lock status synchronized with the test case. When you change the test case's state or lock status with this option enabled, the test script's state or lock status is also updated.

   This option works only if the test case status or locking of the test case is done manually. It doesn't support the synchronized state when the test case status is modified automatically.

   For example: Test case status is changed to Under Review after adding approval record, but test script status is not affected by this action.