> 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/faq/c142/c146/q406.md).

# ¿Puedo hacer seguimiento y gestionar tareas y defectos en un informe?

Report and Run no es un sistema de seguimiento de defectos. Sin embargo, la versión en la nube tiene algunas funciones que le permiten realizar un seguimiento básico de defectos (o incidencias):

* Se pueden agregar a las imágenes las propiedades de estado, asignado a y fecha de vencimiento
* Se pueden agregar propiedades personalizadas a los informes y elementos&#x20;
* Se pueden agregar imágenes de seguimiento a los elementos&#x20;
* Image Builder se puede usar para crear imágenes del antes y el después

## Relacionado

* [Artículo: Cómo agregar propiedades personalizadas a las imágenes desde el portal web](https://docs.reportandrun.com/manual/es/readme/customization/custom-properties/add-custom-properties-to-images.md)
* [Artículo: Cómo agregar propiedades personalizadas a los informes desde el portal web](https://docs.reportandrun.com/manual/es/readme/customization/custom-properties/add-custom-properties-to-report.md)
* [Artículo: Cómo usar Image Builder en Report and Run: Integrar](https://docs.reportandrun.com/manual/es/report-and-run-integrate/content/image-builder.md)
* [Preguntas frecuentes: ¿Cómo puedo compartir informes en la versión en la nube de la app?](https://docs.reportandrun.com/manual/es/faq/c142/c146/q405.md)


---

# 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/faq/c142/c146/q406.md?ask=<question>&goal=<user_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.
