> 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/test-management/azure-devops-in-avo-assure/logging-bug-in-azure-devops/azure-devops-configuration.md).

# Mapping Avo Assure Test Case with Azure DevOps Work Items

Step-by-step process to configure Azure DevOps with Avo Assure:

1\. Select **project** from Projects list

2\. Select **Manage Integrations**.

3. Select **Azure DevOps** icon, enter **Username**, **API Token**, **URL** in their respective fields and hit the Login button

{% hint style="warning" %}
***Note:*** *Select Remember credentials checkbox if frequently working on Azure DevOps integration is required.*
{% endhint %}

4. Select **Azure DevOps** Project and select **Azure DevOps Work** Items from dropdown to link Test Cases with Azure DevOps User story

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FDMcD4lVhTiYo8IaE75lV%2Fimage.png?alt=media&amp;token=590b15ec-e19b-4b22-9363-37d10b5dfe27" alt=""><figcaption></figcaption></figure>

5. Select **Test Case** and Azure DevOps user story checkboxes
6. Click **Map Selected Items** button to map Test Case with Azure DevOps user story.

{% hint style="warning" %}
***Note:** Avo Assure provide only one-to-one mapping of Test Case and user story*
{% endhint %}

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FXuvv7KW3IwH5vQsszBHf%2Fimage.png?alt=media&amp;token=7df90ac0-1625-4b8b-9bb2-2b5d3afa1e53" alt=""><figcaption></figcaption></figure>

7. Click **Save** button located at top right corner to save the mapping
8. Click **View Mapping** tab to view mapped user stories

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FacOoOYMhgAkFhpbXAFmK%2Fimage.png?alt=media&amp;token=91f8b7d3-eb89-4897-9e9a-a42d9c503bb4" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/test-management/azure-devops-in-avo-assure/logging-bug-in-azure-devops/azure-devops-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
