What Is a Duplicate Bug Report?

Duplicate bug reports are inevitable: any bug that affects more than one player will be reported more than once. The instinct is to treat duplicates as clutter to delete, but that throws away one of your best signals. A duplicate is not noise, it is a data point telling you another player hit this bug. Understanding what duplicates are and how to handle them, merge, do not delete, is central to making sense of bug volume.

Why Duplicates Happen

Duplicates are a natural consequence of a bug affecting multiple players. If a crash hits a thousand people and a fraction of them report it, you get many reports of the same underlying issue. They are 'duplicates' only in the sense that they share a root cause; each one is a genuine, independent observation of the bug by a different player. The more players a bug affects, the more duplicates it generates.

This is why duplicate volume is meaningful: it tracks reach. A bug reported once might be an edge case; the same bug reported two hundred times is hitting a lot of people. The number of duplicates is a direct, if rough, measure of how widespread a bug is, which is exactly what you need for prioritization.

Merge, Don't Delete

The correct handling of duplicates is to merge them into a single canonical issue, not to delete them. Deleting destroys the count (your reach signal) and orphans the reporters (you can no longer notify them when it is fixed). Merging preserves both: the issue accumulates an occurrence count reflecting how many reports came in, and every reporter stays attached so you can update them all at once when you resolve it.

Merging also consolidates information. Each duplicate may contain a slightly different detail, a different platform, a different triggering action, and merged together these variations often reveal the root cause that no single report contained. So duplicates are not just a count; collectively they are a richer picture of the bug than any one report alone.

Automatic Deduplication

Manually spotting and merging duplicates does not scale, especially for crashes at volume. The solution is automatic grouping: reports that share a signature (for crashes, derived from the stack trace) collapse into one issue automatically, with a running occurrence count. This turns a flood of duplicates into a single ranked issue without manual effort.

Bugnet's occurrence grouping does this automatically: matching crashes and reports roll up under one issue with a count, and you can also merge duplicates manually when automated grouping does not catch them. The result is that duplicate volume becomes a clean prioritization signal, your dashboard shows distinct issues sorted by how many reports each has, rather than a stream of repetitive reports, and resolving the one issue handles every duplicate and every reporter at once.

A duplicate report isn't clutter, it's a vote on how widespread the bug is. Merge them to keep the count, never delete them.