> For the complete documentation index, see [llms.txt](https://process.mad.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://process.mad.co/project-work/design/bug-reporting-template.md).

# Bug Reporting Template

* **OS:** Android, iOS or Both
* **App Version:** i.e. 1.9.92
* **App** **Build:** xx
* **Environment:** Production or UAT
* **Description of issue:**
*  **Steps to reproduce Issue**
* **What you expected to happen:**
* **What actually happened:**
* **More details:**
  * i.e. Attached screenshots of the issue to give more context on the bug.
* **Add priority tags (please see below)**
  * High - critical issues.
  * Medium - important issues that need to be resolved but not immediate attention
  * Low - low priority issues.

Note: Before you file a new bug, please check to see if it has already been filed in the project. If it has, heart or comment on the existing task to indicate that you've experienced the same bug (instead of adding another task).

<br>


---

# 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://process.mad.co/project-work/design/bug-reporting-template.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.