Linear

Tickets file into the team and intake state you choose, with the screenshot uploaded natively.

Rebase files tickets into the Linear team and intake state you choose — screenshot uploaded natively, triage in the description, status synced both ways.

Connect

1. In the widget, open Settings → Integrations → Linear.
2. Authorize via OAuth.
3. Pick the team and the intake state new issues should land in.

Reports don't pile into a generic inbox — they enter your workflow already routed.

What a ticket becomes

A Linear issue in the team you chose:

• The screenshot uploaded natively to the issue — not linked from elsewhere.
• The AI triage — summary, severity, repro steps, type — in the description.
• A rebase label plus the AI's classification.
• A link-back attachment to the full Rebase report.
• The suspected source location when available — see Source attribution.

Auto-create is a per-integration toggle; creation runs as a queued job with retries. You can also push any ticket manually from its thread.

Status, both ways

Your board is the truth: as the issue moves through your Linear workflow, the Rebase ticket follows. Close it in Linear and the ticket resolves — the pin leaves the page; reopen it and the ticket reopens. Inbound sync arrives via signed webhooks, and each direction is toggleable.

Field mapping

Map Rebase priority and status into Linear's fields and workflow values from the integration's settings.

The badge

Tickets linked to Linear show their identifier — ENG-142 — as a badge in the widget (owners and team only) that jumps straight to the issue.