> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/dashboards/drilldown-to-details-from-a-chart.md).
# Drilldown to details from a chart
Maximize charts for deeper insights - view project trees, apply filters, and drill down to grouped data without changing widget settings. Easily reset to your dashboard view anytime.
For a deeper analysis of a single chart, maximize it. You can do this either by clicking the maximize button  or simply by clicking inside the widget. You will now see your aqua project tree on the left and a filter selection on the right. This allows you to easily apply the widget to other projects or subfolders, or further refine the data in the widget using filters or views. This does not affect the configuration of the widget itself and can be reset by clicking Reload saved configuration or by returning to the dashboard.
Applying the chart to the subfolder of the project and filtering the data
By clicking into the widget itself, the items from the selected grouping of the widget are displayed below the widget (e.g. all defects in the status "To do").
A click on the ID opens the respective item directly, and the button  opens all the items from the selected grouping in the item browser of the navigation.
Opening the chart's element on the navigation tab
---
# 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.aqua-cloud.io/documentation/dashboards/drilldown-to-details-from-a-chart.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.
