# A bug triage process for small teams (with a script you can copy)

> Bug triage is deciding, for each new report, whether it is real, how bad it is, and what happens next. Done well, it takes minutes a day and keeps the bug list honest.

Source: https://cbse.club/guides/bug-triage-process · Updated 2026-11-03

### The goal of triage

Triage is not fixing. It is **deciding**. Every new report should leave the inbox with one of four outcomes:

1. **Accept** – it is real and worth fixing; move it into the workflow.
2. **Need info** – ask a specific question and wait.
3. **Not now** – real, but not worth doing soon.
4. **Close** – duplicate, cannot reproduce, or working as intended.

### What a good report contains

- What happened (with a screenshot or error message).
- What the person expected.
- Steps to reproduce.
- Where: browser, device, app version, account.

Put this list in a pinned card or the board description so reporters see it.

### The one-minute triage script

1. **Is it a duplicate?** Search for it (in CBSE.CLUB press /). If yes, comment a link and close.
2. **Can I understand it?** If not, ask one specific question and leave it.
3. **How bad is it?** Tag severity: `#p1` blocks customers or loses data; `#p2` is a real problem with a workaround; `#p3` is cosmetic.
4. **Where is it?** Tag the area (`#web`, `#api`, `#billing`).
5. **Decide:** accept into Confirmed, send to Not Now, or close with a reason.

### Who triages?

Rotate it weekly. One person (the “triage captain”) owns the inbox that week. Rotation spreads knowledge of the product and stops one person burning out. The captain does not have to fix anything; they decide and route.

### How often?

Daily for products with customers; weekly for internal tools or side projects. Set a time and keep it short. If triage takes more than 15 minutes, you are fixing, not triaging.

### Bug triage in CBSE.CLUB

- New cards land in [Maybe?](https://cbse.club/features/maybe-triage), which is your triage inbox.
- Press number keys to move the focused card into a column, n for Not Now, d to close.
- Gild `#p1` bugs so they sit on top of Confirmed.
- Set auto-postpone to 30 days on the bug board: reports nobody has touched in a month quietly move out.
- Add a Slack [webhook](https://cbse.club/features/webhooks-and-api) for new cards so reports are seen quickly.

Start from the [bug tracking template](https://cbse.club/templates/bug-tracking).

### Should you aim for zero bugs?

Aim for *zero untriaged* bugs. A product with no known bugs usually means nobody is reporting them. A short, honest Confirmed column and an empty inbox is the healthy state.

## Frequently asked questions

### What is bug triage?

Bug triage is the process of reviewing new bug reports to decide whether each is valid, how severe it is, and what should happen next: fix, ask for more information, defer, or close.

### How often should we triage bugs?

Daily for customer-facing products, weekly for internal tools. Keep sessions short and focused on decisions.

### What are bug severity levels?

Many teams use three: P1 blocks users or loses data, P2 is a real problem with a workaround, P3 is minor or cosmetic.
