> For the complete documentation index, see [llms.txt](https://docs.cloudbeat.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudbeat.io/references/untitled-4.md).

# Reports

## The reports screen

This screen is where you can find certain reports by either Release, Project , or Environment.

### Release Report

1. Select a project from the list in the drop-down list, if you haven’t any projects, make sure to check how to create one [here](/references/projects.md).
2. Select range of time for the report in the list to the right.
3. Click on “Show Report”

Now you will see a full detailed report as “Pie chart” , and if you scroll down a bit you will get fully detailed results per releases / cycles, and once you click the certain cycle - you will get a list of tests that was executed under that cycle with their status, passed or failed.

### Project Report

1. Select a project from the list in the drop-down list, if you haven’t any projects, make sure to check how to create one [here](/references/projects.md).
2. Select range of time for the report in the list to the right.
3. Click on “Show Report”

Now you will see a full detailed report as “Pie chart” , and if you scroll down a bit you will get fully detailed results per releases / cycles, and once you click the certain cycle - you will get a list of tests that was executed under that cycle with their status, passed or failed.

### Environment Report

1. Select a project from the list in the drop-down list, if you haven’t any projects, make sure to check how to create one [here](broken://pages/-LuhbxJGIkshc9yWfyy0).
2. Select range of time for the report in the list to the right.
3. Click on “Show Report”

Now you will see a full detailed report as “Pie chart” with environment data as well.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cloudbeat.io/references/untitled-4.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.