Before you edit a clash test or its results, you have to check out the clash test. This locks the test for other project members and ensures that no one overwrites your unsaved changes.

While you are editing a clash test or its results, all your changes are stored locally. Other project members can't see them yet.

When you relinquish a clash test, your changes are synced with the cloud. This unlocks the clash test for other project members.

A clash test is relinquished automatically after running clash detection or a sync with the issue tracker.

Project members that have enough rights can force relinquish clash tests that are checked out by others. It is mostly needed when someone is not relinquishing a clash test for a long time and cannot be reached.

• Who can check out a clash test
• Checking out clash tests
• Relinquishing clash tests
• Force relinquishing clash tests
• Discarding local changes
• Troubleshooting

Who can check out a clash test

You can check out a clash test if you have one of the following clash test roles:

• Project administrator
• Clash administrator
• Test administrator
• Test results editor

The icon in the Access column shows whether you can edit the clash test.

• <no icon>. You can check out the clash test and then edit it.
• . You can edit the clash test.
• . You cannot edit the clash test.

The status in the Access column shows more detail.

Status	Description	Can I check it out?
<blank>	No one is editing the clash test.	Yes (if you have enough rights).
<your name>	You are editing the clash test on another device.	No. You have to relinquish the clash test on the other device. Then you will be able to check it out on your current device. If you have enough rights, you can force relinquish the clash test on the current device. This will discard the changes that you made on the other device. Then you will be able to check it out.
<another user’s name>	Another project member is editing the clash test.	No. If you have enough rights, you can force relinquish the clash test. This will discard the changes made by another project member. Then you will be able to check it out.
New clash test	You created the clash test but never synced it with the cloud.	You can edit or run the clash test, so there is no need to check it out.
You editing now	You are editing the clash test on this device.	You have already checked out the clash test.
No rights to run/edit	You have no rights to edit or run the clash test.	No.

Checking out clash tests

You can check out a clash test if you have enough rights and it is not checked out by another project member.

To check out clash tests:

1. In the Clash Automation pane, select clash tests.

2. Do one of the following:

   • At the top of the pane, click Check out .
   • Right-click any of the selected clash tests and click Check out.

   • At the top of the settings pane, click Check out.

     If you don’t see the settings pane at the right, click Clash test settings at the top of the Clash Automation pane. 

   If this action is unavailable, you cannot check out some of the selected clash tests. See Who can check out a clash test.

Relinquishing clash tests

You can relinquish clash tests that you are editing. This syncs your changes with the cloud and unlocks the clash test for other project members. We recommend that you relinquish all clash tests when you are done editing them.

• Relinquishing selected clash tests
• Relinquishing all clash tests

Relinquishing selected clash tests

To relinquish clash tests:

1. In the Clash Automation pane, select clash tests.

2. Do one of the following:

   • At the top of the pane, click Relinquish .
   • Right-click any of the selected clash tests and click Relinquish.

   If this action is unavailable, you cannot relinquish some of the selected clash tests because you are not editing them.

Relinquishing all clash tests

To relinquish all clash tests:

• In the In the Clash Automation pane, on the top toolbar, click More , and then click Relinquish all.

Force relinquishing clash tests

Force relinquishing a clash test discards all unsaved changes of the person who checked it out.

We recommend that you force relinquish clash tests only when the person who checked them out is unavailable (for example, they are on vacation and you urgently need to edit the test). In all other cases, we recommend that you contact that person and ask them to relinquish the test.

You can force relinquish a clash test if you have one of the following clash test roles:

• Project administrator
• Clash administrator
• Test administrator

A clash test is force relinquished automatically when a user that checked out the test is deactivated, or deleted, or their role in the clash test is changed to "No rights."

To force relinquish clash tests:

1. In the Clash Automation pane, select clash tests.

2. Right-click any of the selected clash tests and click Force relinquish.

   If this action is unavailable, some of the tests are not checked out, or you do not have enough rights to relinquish them.

Discarding local changes

You can discard the changes that you made in a checked out clash test.

To discard local changes:

1. In the Clash Automation pane, select clash tests.
2. Right-click any of the selected clash tests and click Discard local changes.
3. In the Confirmation dialog box, click OK.

This discards the changes and relinquishes the clash tests.

Troubleshooting

Q: Is there a way to recover my changes that were discarded after force relinquishing a clash test?

A: You can recover your changes only if no one submitted a new clash test version after the clash test was relinquished.

To recover the changes:

1. Sign in to the Revizto application on the device where you previously made changes to the clash test.
2. Check out the clash test. Your changes will be restored from a local cache.
3. Relinquish the clash test.