Rebase

Rebase + Linear. Straight to your team.

Reports file into the right Linear team and intake state as structured issues — screenshot uploaded, link-back attached, and status synced both ways.

Connect your workspace

Authorize Linear and pick the team and intake state reports should land in.

Reports become issues

Every capture files as a Linear issue with the screenshot uploaded natively.

Status follows the board

Move it through your Linear workflow and Rebase tracks it automatically.

// Routed, not dumped

The right state, every time.

Reports don't pile into a generic inbox. Rebase maps them into the team and intake state you choose, so they enter your workflow already routed.

  • Right team, right intake state
  • Screenshot uploaded natively to the issue
  • A link-back attachment to the full report
Engineering · IntakeENG-142

Pay now button does nothing on checkout

HighBug
teamEngineering
stateIntake
screenshotuploaded natively
link-backattachment → Rebase

created by rebase · routed automatically

// Two-way status

Your board is the truth.

Rebase follows Linear, not the other way round. As issues move across your board, the Rebase ticket tracks them — reporters see progress without pinging anyone.

  • Status syncs back over signed webhooks
  • Map priority and status into Linear's fields
  • Triage summary and severity arrive with the issue

// The details

Everything travels with the issue. Attached automatically.

  • The exact browser, OS and viewport
  • Console errors and warnings, as they happened
  • Failed and slow network requests
  • A full-page screenshot from the moment it was flagged
  • The exact clicks and inputs that led to the bug
  • The flagged element, its selector and component name
  • AI triage: a summary, a severity and the likely source
  • A link back to the full Rebase report

Frequently asked questions

Have more questions? Contact us

You choose — Rebase files every report into the Linear team and intake state you pick during setup.

The Rebase ticket follows automatically. Status syncs both ways, so your board stays the single source of truth.

The flagged element, the last 50 user actions, the last 50 console errors and warnings, the last 50 network requests, a device and environment snapshot, and a screenshot — merged into one time-ordered timeline: Clicked 'Save' → POST /orders returned 500 → TypeError follows.

// More integrations

Works with the rest of your stack. One layer, every tool.

Start shipping feedback faster.

Start your 7-day free trial.