Integrations
Qalibr connects two kinds of tools: where bugs come from (Slack) and where they go to (your issue tracker). Manage both under Settings → Integrations — connect Qalibr to the tools your team already lives in.
Slack — where bugs come in
Qalibr listens to the Slack channels you choose. To report a bug, post in a
watched channel and mention @Qalibr. (Prefer a keyword? An admin can
configure one — !bug by default — instead of the mention.) Qalibr only reads
the channels you’ve selected; you can change the selection any time.
Linear — where bugs go
Approved bugs become Linear issues. When Qalibr finds a strong duplicate, it can comment on or reopen the existing issue instead of creating a new one. Linear is the supported tracker today.
| Tracker | Status |
|---|---|
| Linear | Supported |
| Jira | Coming soon |
| GitHub Issues | Coming soon |
| GitLab Issues | Coming soon |
Connection health
Each integration shows a status so you know it’s working:
| Status | Means |
|---|---|
| Healthy | Connected and active. |
| Stale | Connected, but quiet — no Slack events in a while, or no tracker sync recently. Worth a check. |
| Disconnected | The connection dropped and needs reconnecting. |
| Not connected | Not set up yet. |
A Stale Slack channel usually just means it’s quiet. If you expected
activity, double-check you’re posting in a watched channel and mentioning
@Qalibr.