> 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.md).

# Logging Bug in Azure DevOps

Avo Assure’s integration with Azure DevOps helps users to map Avo Assure Test Cases to Azure DevOps work items. Mapping establishes a connection between Test Cases and User stories.

Integration of Azure DevOps in Avo Assure is unidirectional. This functionality allows the users to log defects on Azure DevOps based on analysis of reports generated by Avo Assure. The main objective of Logging a Bug is to easily identify, and handle software error found during QA phase.

### This document includes:

[**Pre-requisites**](/avo-assure/integrations-in-avo-assure/test-management/azure-devops-in-avo-assure/logging-bug-in-azure-devops/pre-requisites.md)

The pre-requisite to follow to perform integration

[**API Token generation in Azure DevOps**](/avo-assure/integrations-in-avo-assure/test-management/azure-devops-in-avo-assure/logging-bug-in-azure-devops/api-token-generation-in-azure-devops.md)

The steps to generate API Token in Azure DevOps

[**Azure DevOps configuration**](/avo-assure/integrations-in-avo-assure/test-management/azure-devops-in-avo-assure/logging-bug-in-azure-devops/azure-devops-configuration.md)

The steps to configure Azure DevOps in Avo Assure

[**Logging an Issue**](/avo-assure/integrations-in-avo-assure/test-management/azure-devops-in-avo-assure/logging-bug-in-azure-devops/logging-a-bug.md)

The steps to log issue in Azure DevOps via Avo Assure Reports


---

# 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.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.