Dashboard guides

Dispatch to Slack (Linear + GitHub coming soon)

Connect Slack once per project and BugJar automatically routes every finalized report into that channel — replay link + metadata, never the raw blob. Linear and GitHub dispatchers are on the near-term roadmap.

Most teams already triage bugs in Slack threads, Linear projects, or GitHub Issues. Once you connect Slack to a project, BugJar automatically pushes each finalized report into the connected channel — no manual step on your side. Slack is live today; Linear and GitHub dispatchers are next.

Connect

Go to Settings → Integrations. The page lists each of your team's projects with its current Slack connection state.

  • Slack — connect a Slack channel per project. The OAuth flow installs the BugJar app into your workspace and asks you to pick the channel for that specific project; reports from that project land in that channel. Each project is independent — connect some, leave others disconnected. Available on Solo and Team.
  • Linear (coming soon) — will grant BugJar write access to your team's issues and let you pick the team, status, and labels for dispatched reports. Team tier when shipped.
  • GitHub (coming soon) — will install a BugJar GitHub app on your org with a configurable repo + label. Team tier when shipped.

If a project's Slack token is revoked at Slack's end (someone uninstalled the app, the workspace was deleted), the dashboard surfaces a reconnect prompt on that project's row. Each project is reconnected independently.

Dispatch

Dispatch is automatic. When a report finalizes (the user clicks Send in the consent panel), the SDK uploads the blobs, the API verifies them, and the new report fans out to every enabled integration on that project. There's no Dispatch button on the report-detail page; the message is already in Slack by the time you open the report.

Each delivery includes:

  • The report description (what the user typed before sending).
  • A short metadata line: page URL, browser, viewport.
  • A signed link to the replay viewer in your BugJar dashboard.

Dispatch destinations do NOT receive the raw blob, the audio file, or the unredacted payload. The replay link is gated to authenticated team members.

Webhook delivery retries on transient failure: up to 3 attempts total, with exponential backoff (~2 min, then ~4 min, capped at 60 min). Non-retryable responses (4xx like 401, 404) abandon immediately. If all 3 attempts fail the delivery is marked abandoned and no further attempts are made — the report itself stays in the inbox, only that one dispatch was lost. There is no in-dashboard manual replay yet; the recovery path today is to fix the cause (e.g. reconnect Slack from Settings → Integrations if the workspace token was revoked) so the next report dispatches cleanly.

What happens at the destination

  • Slack — a formatted message lands in the project's connected Slack channel: description + replay link + metadata line. Threading and emoji reactions work normally. (Slack's incoming-webhook API doesn't return a permalink to the posted message, so BugJar can't auto-link the report back to the Slack thread — paste a permalink into the ticket URL field manually if you want that round-trip.)
  • Linear (coming soon) — will open a new issue with the description, replay link, and your configured labels. The Linear issue URL will auto-populate the report's ticket URL field.
  • GitHub (coming soon) — will open a new issue in the configured repo with the same content + label. Same auto-link behavior.

Disconnect

You can revoke any integration at any time from Settings → Integrations. BugJar stops dispatching to it; previously-dispatched reports remain in the destination.