> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/versioning/azure-devops/version-history.md).
# Azure DevOps Actions
{% hint style="info" %}
**Note**: The following steps are the same for all artifacts (Element Repository, Reusable Library, End-to-End and Execution).
{% endhint %}
To view Azure DevOps actions in Test Case page, perform the following actions:
1. On the **Home** page, under **Projects**, select the required **Project**.
2. Select **Design Studio** > **Test Case**.
3. On the **Test Case** page, select the required sub folder.
4. Select the **Ellipsis** (**...**) icon beside the test case.
5. Select **Azure DevOps actions**. The**Azure DevOps actions** dialog opens.
{% hint style="info" %}
**Note**: The context menu option and dialog name depend on the versioning tool configured for the project.
{% endhint %}
The following information applies when the **Azure DevOps actions** option is selected for a test case:
A dialog box appears and displays a tabular view of all previous commits associated with the selected test case.
The Azure DevOps actions table includes the following columns:
* **Assigned to**: Displays the name of the user assigned to the selected test case.
* **Status**: Displays the status of the selected test case. For example: InProgress, or New.
* **Date of push:** Displays the date when the test case version is committed.
* **Username:** Displays the name of the user who commits the test case.
* **Comment:** Displays the comment added during the commit to describe the changes.
* **Branch:** Displays the branch to which the test case is pushed.
6. Hover over the required row and select the **ellipsis** (**⋮**) icon. The following options appear:
* **Restore test case**
* **Restore to new test case**
* **Compare with current**
Restore test case
The Restore test case option restores the selected test case version to the current test case folder, allowing access to the previously committed version.
To restore the selected test case version to the current test case, perform the following actions:
1. Select **Restore test case**. The **Restore test case** dialog opens.
2. Select **Restore**. The restoration process starts and takes some time to complete. \
**Note**: you can also select **Back** to return to the previous screen.
3. After the process completes, the restored test case appears on the **Test Case** page.
Restore to new test case
The Restore to new test case option creates a new test case using the selected test case version and allows it to be added to a new test case . \
\
To restore the selected test case version as a new test case, perform the following actions:
1. Select **Restore to new test case**. The **Restore to new test case** dialog opens.
2. Select the required user from the **Assigned to** list to assign the restored test case. (If required)
3. Select the **Add to new folder?** checkbox. (if required)
{% hint style="info" %}
**Note**: To add the test case to a new folder, select this option and enter the folder name.
{% endhint %}
4. Enter new folder name in the **Folder name** text box.
5. Select **Restore**. The restoration process starts and takes some time to complete.
{% hint style="info" %}
**Note**: You can also select **Back** to return to the previous screen.
{% endhint %}
After the process completes, a new folder is created, and the restored test case appears within the newly created folder.
Compare with current
The Compare with current option compares the selected test case version with the current test case and displays the differences before you restore or update the test case.
To compare the selected test case version with the current test case, perform the following actions:
1. Select **Compare with current**. The comparison dialog opens.
After the process completes, the comparison view appears and displays the differences between the selected from Avo and the pushed test case in Bitbucket.
Review the differences between the **Current View** and the **Pushed Version**. The comparison view highlights change as **Added**, **Edited**, **Removed** or **No Changes**.
{% hint style="info" %}
**Note**: If multiple test cases are selected, select the navigation arrows (**< >**) to navigate between the test cases.
{% endhint %}
2. Select **Done** to close the comparison view.
{% hint style="info" %}
**Note**: From the comparison view, you can restore the multiple test cases at a time by selecting global level **Restore test case** or **Restore to new test cases** options in the Azure DevOps actions dialog.
{% endhint %}
7. Select **Done**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/versioning/azure-devops/version-history.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.