Qalibr documentation
Qalibr turns the bug reports your team already posts in Slack into triaged, deduplicated, routed tickets — without anyone filling out a form. This is your guide to getting set up and understanding how Qalibr reads, scores, and routes every report.
Sign up, connect Slack and your tracker, and watch your first bug get triaged — end to end in under 30 minutes.
QuickstartHow triage works: severity, the Signal score, duplicate detection, and calibration — in plain product terms.
Core conceptsIntegrations, approving and rejecting, and managing your account and data.
ReferenceWhat Qalibr does
Someone reports a bug in a Slack channel Qalibr watches. From there, Qalibr:
- Reads the report and pulls out a title, a severity, and the reproduction details.
- Scores it with a Signal score (0–100) so the most important bugs rise to the top of your inbox.
- Checks for duplicates against everything it has already seen, and surfaces the closest matches with a Match score.
- Enriches it into a clean, structured write-up — ready to become a ticket.
- Routes it to your issue tracker when you approve — as a new issue, or as a comment linked to the one it already matches.
Every report lands in your dashboard, scored and sorted. You stay in control: nothing is created in your tracker until someone approves it.
Today Qalibr listens on Slack and routes to Linear. More chat platforms and trackers are on the way.
Where to start
New to Qalibr? Begin with the Quickstart — it walks the whole path from sign-up to your first routed ticket. Want to understand the scoring and deduplication first? Read Core concepts.