# Bug priority definitions

## p0 bug

{% hint style="info" %}
Ideal time to deploy fix: within 24 hours
{% endhint %}

* App is crashing / none of the users can use the app (e.g.: enroll a new patient, or record a patient's blood pressure)
* Loss of data anywhere in the system
* Fix immediately, all hands on deck!

## p1 bug 

{% hint style="info" %}
Ideal time to deploy fix: within 48 hours
{% endhint %}

* Some nurses are facing severe issues with the app
* Nurses can't use other features of the app (e.g.: view the Progress tab)
* Admins cannot use the dashboard
* Incorrect data being displayed in reports (in the app or on the dashboard)
* Fix urgently!

## p2 bug 

{% hint style="info" %}
Ideal time to deploy fix: within 2 weeks
{% endhint %}

* Bug makes app or Dashboard difficult to use
* Bug may cause errors in analysis in the Dashboard
* Will likely annoy a large group of users
* Fix quickly, but not urgent

## p3 bug 

{% hint style="info" %}
Ideal time to deploy fix: within 2 months
{% endhint %}

* Bug does not affect regular use
* Bug is more of an annoyance than a critical issue
* Bug is a polish issue


---

# Agent Instructions: 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:

```
GET https://docs.simple.org/contact/support/bug-priority-definitions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.