Linear integration

Connect Feedjolt to Linear to push feedback posts into your Linear workflow. When the Linear issue ships, Feedjolt's status updates automatically - and your customer gets a notification.

What it does

• One-click "Send to Linear" on any Feedjolt post. Creates a Linear issue with the title, body, and a back-link.
• Bidirectional status sync - when the Linear issue moves to "Done", the Feedjolt post moves to "Shipped". (Mapping configurable.)
• Comment sync - bidirectional and optional: staff comments sync to the Linear issue, and Linear comments come back as internal notes.
• Author attribution - the Linear issue is created by the Feedjolt admin who clicked "Send to Linear", with the original feedback author noted in the body.

Install

1. Dashboard -> Integrations -> Linear.
2. Click Connect to Linear.
3. Approve the OAuth scope on Linear. You'll need to be a Linear workspace admin or have permission to install third-party apps.
4. After redirect, pick the Linear team you want feedback to sync into.
5. Map Feedjolt statuses to Linear workflow states (e.g. Planned -> Backlog, In progress -> In Progress, Shipped -> Done).

Permissions Linear requests

We don't read your existing Linear issues. We only see what we created.

Sending a post to Linear

On any Feedjolt post:

1. Click Send to Linear in the action bar.
2. Pick the team (defaults to the team you mapped at install).
3. (Optional) edit the title or body.
4. Click Create issue.

The Linear issue is created and a link appears on the Feedjolt post. Anyone viewing the post sees the link (admins) or a "Tracked in our project tracker" badge (end users).

Status sync

When the Linear issue moves between workflow states, Feedjolt receives a webhook from Linear and applies the configured mapping.

Status sync is governed by the workspace-level Sync status changes bidirectionally toggle - there is no per-post status-sync setting. When it's on, it applies to every linked post: moving a linked Linear issue's workflow state updates the mapped Feedjolt status, and changing a Feedjolt post's status moves the linked Linear issue (and vice-versa).

If you change the mapping later, only future status changes use the new mapping. Existing posts keep their last-applied status.

Comment sync

Turn this on with the Sync comments checkbox in Settings -> Integrations -> Linear. It is bidirectional and controlled by that single toggle.

• Outbound - comments from workspace members (staff) on a linked post, both public replies and internal notes, are posted to the linked Linear issue, prefixed with the author's name.
• Inbound - comments on the Linear issue appear in Feedjolt as internal notes (visible to staff only, never shown on the public portal), prefixed with the Linear author's name (e.g. "Jane via Linear").
• End-user comments stay put - comments from your customers are not synced to Linear.
• Loop-safe - a comment mirrored in one direction is never echoed back.

Prerequisite: Linear comment webhooks must be enabled on the Feedjolt Linear app. In Linear, a workspace admin must enable the Comments resource on the app's webhook (Settings -> API -> your app/webhook), in addition to Issues. Until that's enabled, inbound Linear -> Feedjolt comment sync won't fire.

Bulk send

In the dashboard, select multiple posts and click Bulk -> Send to Linear. Each post becomes a separate Linear issue.

For products with many small feedback items, consider grouping by tag and sending one Linear issue per tag instead - your engineering team will thank you.

Disconnecting

Dashboard -> Integrations -> Linear -> Disconnect.

Existing Linear issues stay in Linear; the link from the Feedjolt post stays as a plain URL (no longer auto-syncs). Reconnecting picks up where you left off.

Limitations

• One Linear team per Feedjolt workspace in the basic mapping. Per-board mapping is on the roadmap.
• No Linear -> Feedjolt issue creation - the flow is one-way (Feedjolt to Linear).
• No attachment sync - Linear's attachment API is rate-limited; we don't push attachments yet.
• Extreme bursts are throttled (a runaway guard well above normal traffic). Linear retries a throttled delivery, but its retry budget is finite - a very large bulk edit can still leave a few statuses out of sync. If you've just done a mass update in Linear, spot-check the affected posts.

If any of these matter, let us know.