In-app bug reports bridged to GitHub Issues

Any member of any tenant reports a bug from inside the app; the product team works it in GitHub Issues; the member sees the status and the team's replies without leaving the app.

The idea the design turns on: the local row is the record, the tracker follows it, and the tracker owns the status. A report is saved under the tenant's policies first and reaches GitHub through an outbox, so a GitHub outage delays it and loses nothing. Status is written only from GitHub's own state, so the app and the tracker can never disagree about whether a bug is fixed.

Written by the engineer who has shipped this module, audited against the earlier implementation, the bug report bridge of a multi-tenant console on Next.js 16, Vercel and Supabase. The templates hold what such a bridge must: one issue per report however often a job retries, no team comment shown to a tenant without an explicit opt-in, no attachment reachable without a sign-in, and workers that run on any host. provenance.md has the record.

When to use