# What is Bug Report?

> A write-up of unexpected behavior with enough detail for an engineer to reproduce it.

Canonical: https://www.decimal.app/glossary/bug-report · Last reviewed: 2026-09-23

A bug report describes a defect: what the user expected, what happened instead, the steps and environment that produce it, and any supporting evidence like logs, screenshots, or request IDs.

## Why it matters

The quality of a bug report sets how fast engineering can act. A vague report triggers a round of questions back to support and the customer, which can add days before anyone looks at the code.

## Best practices

1. Include identifiers. Account ID, request ID, timestamps with time zone, and the product version.
2. Separate fact from guess. State what was observed, then label any hypothesis as one.
3. Link the customer impact. Note how many customers and how much revenue are affected so it can be prioritized.

## How Decimal helps

When Decimal escalates, it writes the bug report for you: reproduction details, the suspect code path, and the evidence that points there.

## Related terms

- [Reproduction (Repro)](https://www.decimal.app/glossary/reproduction): Making a reported bug happen again on purpose to confirm and study it.
- [Engineering Escalation](https://www.decimal.app/glossary/engineering-escalation): A ticket support hands to engineering because it needs code-level investigation.
- [Severity Level](https://www.decimal.app/glossary/severity-level): A rating of how much harm an issue is causing, from outage to cosmetic.
- [Known Issue](https://www.decimal.app/glossary/known-issue): A confirmed bug that's been acknowledged but not yet fixed.

---

Decimal · Book a demo: https://cal.com/decimal-demo/30m · Markdown index: https://www.decimal.app/llms.txt