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

# Logging a Bug from Result Summary

In Avo Assure we have two Defect management tool Jira & Azure DevOps

### Prerequisites for before logging bug in Jira from report section

1. Jira credentials: Ensure to keep Jira login credentials ready
2. Jira URL: Ensure to keep saved Jira URL ready 
3. Jira Token: Generate and keep the Jira API Token handy
4. Jira configuration: Ensure to Jira configuration is done already

### Prerequisites before logging bug in Azure DevOps from report section

Azure DevOps Username: Ensure to keep Azure DevOps login credentials ready 

Azure DevOps API Token/Password: Generate the API token or password to use during login

Azure DevOps URL: Keep the Azure DevOps URL ready\
Azure DevOps configuration: Ensure Azure DevOps configuration is done already


---

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