Skip to lesson
Exit
Bug Triage & Prioritization at Scale1 / 2

1 min lesson

Canonical issue plus linked duplicates

Make the call in this situation. "Twelve new reports describe the same Tab failure and carry the same stack trace. A teammate suggests closing eleven as duplicates to keep the board clean. What do you do?" Explain what supports it.

Step 1 of 2

Canonical issue plus linked duplicatescount once, count right

Pick one canonical issue per cluster and link every duplicate to it. Resist the urge to just close dupes. Each linked report is a unit of volume and a different repro environment, and the live count is what you'll cite to engineering. A cluster of 1 and a cluster of 600 need the same canonical record but produce very different priorities.

  1. 1Open or find the canonical. One issue per real defect, named by symptom and area, not by the loudest ticket.
  2. 2Attach evidence. Roll the strongest repro, logs, versions and affected accounts up to the canonical.
  3. 3Link, don't delete. Point duplicates at the canonical so volume and ARR stay countable.
  4. 4Recount on every new report. Volume, ARR affected and trend direction update live. That's the prioritization input.