> For the complete documentation index, see [llms.txt](https://engineering.umh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engineering.umh.app/engineering/development-process/how-to-build/tickets/bugs.md).

# Bugs

What a bug is, where its ticket goes, and who owns it.

Owner: Jeremy

A bug is anything a user can run into today where the product does not work as they would expect.

## Rules

* Whoever finds a bug files it under a sub-ticket called Bugs, inside the [rollout ticket](/engineering/development-process/how-to-build/tickets/rollout.md) or [monitoring ticket](/engineering/development-process/how-to-build/tickets/monitoring.md) of its feature.
* How likely users are to run into a bug sets its priority.
* A bug we decide not to fix now stays open, and the owner writes why in a comment.

## What counts as a bug

**A problem no user has seen yet is still a bug.** So are wrong docs and gaps in our own error reporting and telemetry. If only a future change to the code can trigger a problem, it is [tech debt](/engineering/development-process/how-to-build/tickets/tech-debt.md). A request for something we don't offer is a [rollout ticket idea](/engineering/development-process/how-to-decide-what-to-build.md#rollout-tickets).

For example, the CPU status divides by the time between two measurements. When that time is a few microseconds, it shows about 70 cores on a 4-core machine.

## Where a bug ticket lives

**The title starts with `[BUG]`.**

**If no feature fits, file it under the monitoring ticket of that area of the product, or else under the monitoring ticket for the maintenance of that repository.**

**If you are not sure a user can run into it, file a bug.** If the owner finds that only a future change to the code can trigger it, they move it to tech debt and write why.

**Who decides how to fix a bug, or not to fix it now, works as in** [**Obvious tech debt and decisions**](/engineering/development-process/how-to-build/tickets/tech-debt.md#obvious-tech-debt-and-decisions)**.**

* A security bug goes under the Security sub-ticket instead, as [Security](/engineering/development-process/how-to-build/tickets/security.md) describes.
* A customer's bug starts as a [customer request](/engineering/development-process/how-to-decide-what-to-build/signals/customer-requests.md), blocking or not.
* A Sentry issue finds its ticket through its [feature tag](/engineering/development-process/how-to-build/coding-standards/architecture/error-management.md#feature-tags), which is that feature's [public name](/engineering/development-process/how-to-build/tickets.md#public-names).


---

# 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://engineering.umh.app/engineering/development-process/how-to-build/tickets/bugs.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.