> 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/logging-a-bug.md).

# Logging a Bug in Azure DevOps

Bug logging involves, reporting a bug and providing a detailed description to resolve the bug.

Step-by-step process to log bug in Avo Assure:

Navigate to landing page of Avo Assure

1. On the **Home** page, from **Projects** list, select project.
2. Select **Design Studio**. The **Element Repository** page opens.
3. Select **Reports** page.
4. Click **Test Case Details** button to bring up Run Details window

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F9MwYAP7z2j754v1ebxjx%2Fimage.png?alt=media&amp;token=059bd6c9-0f84-471c-a28b-41bde44e48d9" alt=""><figcaption></figcaption></figure>

3. Click **View Reports** to navigate to Result Summary window

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F1QewtA135bQb6wOyG3xl%2Fimage.png?alt=media&amp;token=69f38360-ac7d-4a1b-80ae-9f079f911f04" alt=""><figcaption></figcaption></figure>

4. Click **>** arrow and expand Test Step Group, click **Bug** icon in Defect column and select Azure DevOps to bring up login pop up on the screen

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F9zRgfVZnCMu2F9FbQm8v%2Fimage.png?alt=media&amp;token=6ddf7e01-db3a-43c7-bcca-a65e4e3560ca" alt=""><figcaption></figcaption></figure>

5. 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%2FQWHE9VFEKYnVAxubVpvx%2Fimage.png?alt=media&amp;token=f8b929a1-3cc3-4c35-bb59-b285b1849bae" alt=""><figcaption></figcaption></figure>

6. Click **Azure DevOps** icon in Defect column to bring up Create Issue pop window on the screen

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2Fqmn4L4ehM0tdmKRDbsdl%2Fimage.png?alt=media&amp;token=518cb051-9e0c-47ab-83c1-7971ff66bf1d" alt=""><figcaption></figcaption></figure>

7. Provide mandatory details and click **Proceed** button

{% hint style="warning" %}
***Note:***

*For more detailed report, click Configure Fields dropdown and select more option.*
{% endhint %}

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F8hMegh7WTxONdBxxFBJj%2Fimage.png?alt=media&amp;token=6480d6d2-7c01-4683-acf2-bc64d93f834c" alt=""><figcaption></figcaption></figure>

8. 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%2FL4autBU4QmHNkki92n5w%2Fimage.png?alt=media&amp;token=95e7c02f-f9dd-467c-999a-8bdc28f729f8" alt=""><figcaption></figcaption></figure>

9. 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%2FYdAcssl8zUjNrWXbbAzQ%2Fimage.png?alt=media&amp;token=d0dd6623-086c-446e-b95e-122d082d8a2a" 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/logging-a-bug.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.