> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/es/report-and-run/filtrar-informes/filtrar-elementos-del-informe.md).
# Filtrar elementos del informe
Usa filtros para crear una vista personalizada de tus informes.
1. Toca un informe para abrirlo.
2. Toca los tres puntos verticales en la barra de herramientas superior derecha.
3. Elige **Filtro del informe** en el menú desplegable.
4. Toca **Añadir (+)** en el centro de la pantalla o desde la barra de herramientas superior.
5. Elija la [condición](/manual/es/report-and-run/filtrar-informes/condiciones.md) que desea usar en el filtro del informe. En el ejemplo siguiente, la *Descripción* condición fue seleccionada.
6. Escriba su término de filtro en el *Buscar* campo o marque la casilla "Sin asignar" para incluir solo los elementos en blanco.
7. Toca **Añadir (+)** en la parte superior de la pantalla para incluir condiciones adicionales.
8. Haga clic en la flecha hacia atrás en la esquina superior izquierda para ver su informe con el filtro activado.
9. El informe filtrado mostrará solo los elementos que cumplan las condiciones que especificó. El *Filtro del informe* El icono indica que el informe muestra una vista filtrada.
10. Cuando salga de la pantalla del informe, este volverá a la vista predeterminada sin filtrar.
---
# 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.reportandrun.com/manual/es/report-and-run/filtrar-informes/filtrar-elementos-del-informe.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.
