> 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/create-and-execute-tests-with-design-studio/working-with-reports-section/log-a-bug-from-view-report/azure-devops.md).

# Logging a Bug in Azure DevOps

Follow the steps below to log a bug in Azure DevOps from reports section

1. Navigate back to the Report tab and click Testcase Details icon, to bring up Run details popup window in top right corner of Reports tab

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FpKZeRNZZIQJPON0HraW8%2Fimage.png?alt=media&amp;token=e095349d-a3a9-4a30-80c1-7aac4f15ee31" alt=""><figcaption></figcaption></figure>

2. Click view Reports icon, from Run Details pop up window to bring up Result Summary window in screen.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FEGbMKCBcX4z8fkT2Gra2%2Fimage.png?alt=media&amp;token=454fb86c-5c43-4090-97ca-ed9e90df6dd1" alt=""><figcaption></figcaption></figure>

3. Click Expand arrow from the # column to check the detailed analysis of the execution for all the Test Step details of the Test case
4. Click bug icon from Defect column to access defect management tools.
5. Select Azure DevOps option to bring up Azure DevOps pop up on screen

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FJ6L2fPVFPQ8haSjG2W3k%2Fimage.png?alt=media&amp;token=52e06be1-be00-4e9c-a778-59671f8c2bb8" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Note: *after selecting Azure DevOps option it will bring up auto fill pop up on screen*
{% endhint %}

6. Enter credentials and URL then click Connect button. This will change bug icon to Azure DevOps icon.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FD2seW4tK4LaDcfHauqGs%2FADO_Password_Masking.png?alt=media&amp;token=1fc1618f-8fb8-42aa-add7-8b09e13be597" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FyLKFAxQwBmtS5gOOGjC6%2Fimage.png?alt=media&amp;token=29c4e263-961f-4dcd-9713-4cb57b2c09e7" alt=""><figcaption></figcaption></figure>

7. Click Azure DevOps icon in Defect column to bring up Create Issue pop window on the screen.
8. Select Issue Type, enter Iteration Path, enter Area Path, enter Title, enter State and click Proceed button. For more detailed report, click Configure Fields dropdown and select more option.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FmvyX9XTkfrCJ0WgHiWSN%2Fimage.png?alt=media&amp;token=e4734d8b-1008-46df-a6ab-91a7c421de48" alt=""><figcaption></figcaption></figure>

9. As you click proceed, the Azure DevOps icon changes into Defect Id

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FnIYfoWxPz8ZF96TXrwPe%2Fimage.png?alt=media&amp;token=10ed6922-7df7-4feb-96a5-49c4a36e110e" alt=""><figcaption></figcaption></figure>

10. Click the Defect Id to directly navigate to the Azure DevOps website and see the logged bug 

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FnkWJyQiYEEQB98k20CxF%2Fimage.png?alt=media&amp;token=61d23083-39a5-46c2-9a50-ecd7e44f01bd" 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/create-and-execute-tests-with-design-studio/working-with-reports-section/log-a-bug-from-view-report/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.
