> 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/jira-integration/manual-defect-creation/create-defect-through-reports.md).
# Creating Defect through Reports
{% hint style="info" %}
**Note:** Ensure to have Execution list is created and executed before creating defect through reports.
{% endhint %}
**To create defect through reports, perform the following actions:**
1. On the **Home page**, select **Design Studio**.
2. Select **Reports** tab.
3. In the right pane, Click **Test Case Details** button. **Run Details** pop up window appears.
4. Select **View Report** icon to navigate to **Result Summary** window
5. Expand Test Step group, locate **failed Test Step** and click **Bug icon** in **Defect column.**
6. Select **Jira,** auto populated **login** pop up appears.
7. Click **Connect** button, this will change **bug icon** to **Jira icon**
8. Select **Issue Type**, and **Configure Field** from their respective dropdowns
{% hint style="info" %}
**Note:** For more detailed report, click Configure Fields dropdown and select more option.
{% endhint %}
9\. Enter defect’s **Description**, **Summary**, **Reporter,** **Environment** and click **Proceed** button.
10. After clicking **proceed** button, the **Jira** icon changes into **Defect Id.**
11. Click the **Defect Id** to directly navigate to the **Jira website** and view the logged bug.
---
# 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/jira-integration/manual-defect-creation/create-defect-through-reports.md?ask=&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.
