Integration · Linear
Push Bug Reports + Session Replays To Linear In One Click
Every Linear issue auto-attaches a session replay, console logs, network calls, and AI-generated reproduction steps. Stop pasting screenshots into Slack threads.
What you get
One-click ticket creation
Click "Open in Linear" inside any session — the ticket lands in the right team's inbox with the replay link, console errors, and repro steps already filled in.
Auto-attached evidence
Replay link, browser metadata, network HAR, console logs, Git SHA, and feature-flag state — all appended to the issue body. Every Linear ticket is a complete bug report.
AI repro steps
The generated reproduction steps are written in plain English ("Log in as a free user, click upgrade, observe spinner"), not pixel coordinates. Reviewers can act on them.
Two-way sync
When the Linear ticket closes, the corresponding session is marked resolved in Relyv. When duplicates are auto-merged in Linear, the merge is reflected in Relyv's dashboard.
Setup in four steps
- 1
Connect Linear via OAuth
A workspace admin clicks "Connect Linear" in Relyv settings. Two-factor-friendly OAuth — no API keys to manage, no SCIM provisioning required.
- 2
Map Relyv projects to Linear teams
Pick the Linear team and project that should receive each Relyv project's bug reports. Defaults can be overridden per-issue at creation time.
- 3
Click "Report" inside Relyv
From any session — replay, AI summary, or frustration heatmap — click "Open issue" and choose Linear. Title, severity, labels, and body are pre-filled.
- 4
Issue lands in Linear inbox
The issue appears in the assigned team's inbox with all evidence attached. Linear automation rules can route it further; two-way sync keeps Relyv aware of state changes.
Implementation details
What gets attached to a Linear issue
A direct replay link (Relyv-hosted, password-gateable), a markdown summary of the user's journey through the bug, console errors and warnings, the network HAR file, browser + OS + viewport metadata, the Git SHA at capture time (if release tagging is wired), and the feature-flag state for that user.
Custom workflows and labels
Map Relyv severity to Linear priority (P0–P3). Auto-apply Linear labels based on the page where the bug occurred ("checkout", "auth", "marketing"). Route to specific teams using Relyv project metadata.
Permissions and security
OAuth scopes: read team membership, write issues, read issue state (for two-way sync). No code, repository, or member email access. Token rotation is automatic; revoking from Linear admin instantly cuts access.
Frequently asked
Does this work with Linear Free / Standard / Plus?
All Linear plans are supported. Two-way sync requires Linear Standard or above (Linear's API rate limits on Free are too tight for reliable bidirectional updates).
Can I use custom Linear workflows?
Yes. Map Relyv events to any Linear workflow state. Mapping is per-team, so different teams can have different conventions ("Done" vs "Closed" vs "Shipped").
How does multi-team routing work?
Map Relyv projects (or page paths, or user segments) to specific Linear teams. The router runs server-side and supports rule-based routing — "checkout bugs go to #payments, signup bugs go to #growth".
What about two-way sync when issues are merged?
When two Linear issues are merged (manually or by automation), the merge is reflected in Relyv: both source sessions point to the surviving Linear issue. No duplicate dashboard noise.
Ready to wire up Linear?
Every Linear issue auto-attaches a session replay, console logs, network calls, and AI-generated reproduction steps. Stop pasting screenshots into Slack threads.