Approving & rejecting

Qalibr never changes your tracker on its own. Every bug waits in Review until you make the call.

From the dashboard

Open a bug from the Inbox or the Calibration view. Review the enriched Report and the Signal score, then:

• Approve — routes the bug to your tracker. You can add an optional note for the audit trail. Qalibr confirms with the ticket it created (for example, Approved · routed to ENG-412).
• Reject — dismisses the report. A short reason is required, and no ticket is created.

If Qalibr surfaced duplicate candidates, you’ll also see options to link the report to an existing issue, reopen a closed one, or route it as new. See Duplicate detection.

From the Slack thread

You don’t have to be in the dashboard. When a bug needs a decision, Qalibr replies in the Slack thread with a secure, single-use approval link — approve or reject right there, and the dashboard stays in sync. It confirms the result in-thread too (for example, Approved · routed to ENG-412), so the whole conversation stays in one place.