Linear integration

Turn customer feedback into Linear issues — then close the loop.

Push the requests that matter straight into Linear, keep statuses in sync both ways, and let Feedjolt tell every customer who voted the moment you ship. Product and engineering, finally reading from the same page.

Feedback dies between tools.

Requests pile up in one tool while engineering works in another. Someone copies tickets by hand, statuses drift, and the customer who asked never hears that it shipped. The Linear integration wires the two together so the loop closes itself.

What you get

Feedback and Linear, finally in sync.

One-click Send to Linear

Turn any feedback post into a Linear issue from the action bar — title, body, and a back-link to the original request, no copy-paste.

Two-way status sync

Move the Linear issue to Done and the Feedjolt post flips to Shipped — and the reverse. The mapping is yours to configure.

Auto-notify every voter

When the linked work ships, Feedjolt tells the customers who voted for it. You write zero update emails.

Two-way comment sync

Staff comments flow to the Linear issue; Linear replies come back as internal notes. Optional, loop-safe, and off until you flip it on.

Bulk send

Select a batch of posts and ship them to Linear at once — or group by tag and send one tidy issue per theme.

Prioritized, not random

Send the requests your customers actually voted up, so engineering builds by demand instead of whoever filed the loudest ticket.

How it works

From request to shipped, without the relay.

01
Connect Linear

Approve the OAuth scope, pick the team feedback syncs into, and map Feedjolt statuses to your Linear workflow states.

02
Send what wins

Click Send to Linear on a prioritized post. A Linear issue is created and a link appears on the Feedjolt post.

03
Ship and close the loop

Move the issue to Done in Linear. The Feedjolt status updates and every voter gets the good news — automatically.

Why Feedjolt

Built to keep both teams aligned.

The loop actually closes

Shipping in Linear notifies the customers who asked — the last mile most feedback tools quietly skip.

Sync runs both directions

Statuses stay in lockstep whether the change starts in Feedjolt or in Linear. No manual mirroring.

Engineering keeps its workflow

Issues land in your Linear team with your states and your mapping. No new tracker to learn or babysit.

Live in minutes

One OAuth approval, a quick status mapping, and you're sending feedback to Linear before standup.

Frequently asked, plainly answered.

How does the Linear integration work?

Connect Linear from Dashboard → Integrations, then click Send to Linear on any feedback post. Feedjolt creates a Linear issue with the title, body, and a back-link, and keeps the two statuses in sync from there.

Is status sync one-way or two-way?

Two-way. With the bidirectional sync toggle on, moving a linked Linear issue updates the mapped Feedjolt status, and changing a Feedjolt post's status moves the linked Linear issue — both directions, every linked post.

Do customers get notified when work ships?

Yes. When the linked Linear issue moves to your shipped state, Feedjolt updates the post and notifies every customer who voted for it — so closing the loop takes zero extra effort.

Can I send several posts to Linear at once?

Yes. Select multiple posts in the dashboard and use Bulk → Send to Linear; each post becomes its own issue. For lots of small items, group by tag and send one Linear issue per tag.

Do comments sync between Feedjolt and Linear?

Optionally. Turn on Sync comments and staff comments post to the linked Linear issue, while Linear replies come back as internal notes. End-user comments stay in Feedjolt and are never synced.

Can Linear issues create Feedjolt posts?

No. Issue creation is one-way — Feedjolt to Linear. You send feedback into Linear, not the other way around. The basic mapping also links one Linear team per workspace.

Turn feedback into shipped features.