> 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/zephyr-scale/view-reports-in-zephyr-scale.md).
# Viewing Reports in Zephyr Scale
After executing Test cases in Avo, detailed reports are automatically sent to Zephyr Scale. This ensures that test results are easily accessible for tracking and analysis.
**The reports include:**
* Test case Status
* Test Step Status
* Time Stamp
* Screenshots for Failed Steps
* Avo PDF
* Jira Defect ID
**Follow the steps to view report (Test case Execution Status and Test case Execution Time) in Zephyr Scale are:**
1. Login to Jira with valid credentials and select **Project** from dropdown.
2. Go to **Zephyr Scale** and select **Test Cycle** tab.
3. From **All test cycles** list, select **Test Cycle** which navigates to the **Execution** Reports.
4. In the **Execution Report**,
1. The **green color** represents the status as **PASS,** and the **play** button provides the execution time.
b. The **red color** represents the status as **FAIL** and the **play** button provides the execution time.
i. Expand the **Issues** option to view the bug logged for the failed test case along with the **defect ID.**
ii. Click the **defect ID** to open the **detailed reports** with **Screenshots**.
5. Expand the **Attachments** option to view Avo reports in PDF format, including screenshots.
{% hint style="info" %}
**Note**: Avo **Reports** are automatically attached to **Zephyr Scale**.
{% endhint %}
6. Expand the **Test Script** option to view the **Test Step Status.**
---
# 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/zephyr-scale/view-reports-in-zephyr-scale.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.
