Guides

How to group duplicate bug reports

When several people report the same bug in different words, group the reports so you fix it once and know how many people it affects.

Short answer: match reports by what went wrong, not by the words used. “Total didn’t update”, “price stuck on 3 nights” and “wrong amount at checkout” are one bug. Group them under the first report and count how many people hit it.

Why grouping matters

  • You fix each bug once instead of investigating it five times.
  • The number of reports tells you how urgent it is.
  • You can reply to everyone affected when it’s fixed.

How to group by hand

  1. 1

    Write a one-line summary for each report

    Describe what happened in plain words: “total doesn’t update after changing dates”.

  2. 2

    Match on the problem, not the wording

    Same screen and same wrong result usually means the same bug, even if the words differ.

  3. 3

    Keep one main report

    Link the others to it, and keep each person’s details so you can reply to all of them.

How Bopmigo does this

Bopmigo summarizes every report and links reports about the same problem, even when people describe it differently. The inbox shows “3 related reports” on the report, so the most common problems stand out.

A feature request with related reports grouped below it
Requests about the same thing are grouped.