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

# Can I track and manage tasks and defects in a report?

Report and Run is not a defect tracking system. However, the cloud version has some features that allow you to perform basic defect tracking (or snagging):

* Status, assigned to, due date properties can be added to images
* Custom properties can be added to reports and items 
* Follow-up images can be added to items 
* Image Builder can be used to create before and after images

## Related

* [Article: How to add custom properties to images from the web portal](/manual/readme/customization/custom-properties/add-custom-properties-to-images.md)
* [Article: How to add custom properties to reports from the web portal](/manual/readme/customization/custom-properties/add-custom-properties-to-report.md)
* [Article: How to use the Image Builder in Report and Run: Integrate](/manual/report-and-run-integrate/content/image-builder.md)
* [FAQ: How can I share reports in the cloud version of the app?](/manual/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 dynamically by asking a question.

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

```
GET https://docs.reportandrun.com/manual/faq/c142/c146/q406.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.