Qalibr docs — your guide to bug intake intelligence. Start a free trial →
Core conceptsHow triage works
Core concepts

How triage works

Every bug that comes in runs through the same short pipeline before it reaches you. Qalibr handles the busywork — reading, scoring, deduplicating, and drafting — and leaves the decision to you.

Classify

Qalibr reads the report and works out what it is: a title, a severity, and the reproduction details it can find.

Check for duplicates

It compares the report against everything it has already seen and surfaces the closest matches, each with a Match score.

Enrich

It turns the raw message into a clean, structured Report — the kind of write-up you’d want in a ticket, not a one-line Slack vent.

Route

When you approve, Qalibr creates the ticket in your tracker — or, if it found a strong match, links the report to the existing issue instead of opening a duplicate.

The result lands in your Inbox, scored and sorted, with a clear next action. Nothing reaches your tracker until you approve it.

These stages run in order for every report — you don’t lift a finger. The triaged result simply appears in your Inbox, scored and ready for your decision.

The pieces