Duplicate detection
Most teams report the same bug three to seven times before anyone notices. Qalibr catches the repeats so they don’t each spawn a ticket.
Match score
When a new report comes in, Qalibr compares it to everything it has already seen and surfaces the closest matches, each with a Match score — shown as a percentage (for example, 94% match). The higher the score, the more confident the match.
A match draws on more than wording: a shared error signature, overlapping keywords, and a similar title all push the score up. When a report is thin on detail, Qalibr is deliberately more cautious about calling it a duplicate.
What you can do with a match
When Qalibr surfaces candidates, you choose what happens:
| Action | Result |
|---|---|
| Link to this | Adds a comment to the existing open issue. No second ticket. |
| Reopen as duplicate | Reopens a closed issue and links the new report to it. |
| Reject as duplicate | Marks the report as a confirmed duplicate — no new ticket, no comment. |
| None of these — route as new | None of the candidates fit. Qalibr opens a fresh ticket. |
If nothing clears the bar, there’s nothing to decide — Qalibr simply routes the report as a new bug when you approve it.
Where duplicates live
Bugs that resolve to a duplicate show up under the Duplicates view in the dashboard, and the Dedup rate insight tracks how many repeats Qalibr is catching for you. See The dashboard.