Bug reports that arrive in Linear ready to work
Notarus creates a Linear issue with the report text, source page and signed screenshot or video links when captured. Its backlink opens the Notarus ticket for replay, logs and browser context. The Notarus pipeline maps to your Linear workflow states, so moving an issue in Linear moves the ticket in Notarus and the reverse holds.
Linear integration
Every integration is on every plan, the free one included. No credit card.
Discount code accepted but total unchanged
- Issue title and description
- Media links
- Ticket backlink
- Source page
- Workflow state
What reaches Linear
-
Issue title and description. The report title and body, with steps to reproduce preserved as written.
-
Media links. Signed links to a screenshot or screen recording when captured; no file upload to this provider.
-
Source page. The report’s page URL; captured browser and viewport details remain on the linked Notarus ticket.
-
Ticket backlink. The Notarus ticket links authorized teammates to the available replay, console and network evidence.
-
Workflow state. Status flows both ways. Moving the ticket on the Notarus board moves it in the tracker, and moving it in the tracker moves it back, through a state map an admin sets once per project.
How Notarus and Linear fit together
Linear's appeal is that it stays fast, and the fastest way to slow it down is a backlog of issues that each need a conversation before anyone can start. A bug report written by someone outside the engineering team almost always needs that conversation, because the reporter described what they saw and not the conditions that produced it.
Notarus gathers the available context at report time. The issue that reaches Linear includes the reporter’s description, priority, severity and source page, with signed media links when present. The backlink takes an authorized teammate to the Notarus ticket, where the replay, console output and browser context stay together for investigation. This gives an engineer a place to start before asking the reporter for more detail.
Linear has real workflow states rather than a free-form status field, which makes the state map cleaner here than on most trackers: the mapping suggests itself from your team's actual states. Two are never suggested, Triage and Cancelled, because neither corresponds to a stage in the Notarus pipeline and mapping them would move tickets into a state the board cannot represent.
Teams that use Linear tend to care about the shape of their backlog, and an integration that dumps every piece of raw feedback into it is one they turn off within a week. Which reports get pushed is therefore a project setting rather than a default: the Notarus board can hold everything that comes in, and only the issues somebody has decided are real need to cross over. That triage step happens on the Notarus board, where an unconfirmed report costs nothing, rather than in the backlog where it costs everyone's attention.
Common questions
Which Linear states does Notarus map to?
Your team's own workflow states, suggested from the ones Linear reports and adjustable afterwards. The suggestion maps an open state, an in-progress state and a completed state to the Notarus pipeline. Triage and Cancelled are excluded on purpose, since neither corresponds to a Notarus stage.
Can a Linear issue update the Notarus ticket?
Yes, that is the inbound half of the sync. Moving an issue to a mapped state moves the Notarus ticket to the matching stage, which is what lets the reporter see progress in the portal without anyone updating two systems.
Does the reporter need a Linear account?
No. Reporters follow their own report through the Notarus portal from a link, with no account anywhere. Linear seats stay for the people who work the issues.
Other trackers
Terms on this page: bug triagebug life cycleqa testing
Send your first report to Linear.
Every integration is on every plan, the free one included. No credit card.