Linear issue sync
Connect a Linear team with OAuth. Issues become feedback in the Usero inbox, any feedback item becomes a Linear issue with one click, and completing on either side completes the other. Direction is one setting on the Linear card.
Startup teams run engineering in Linear and collect feedback everywhere else. The gap between the two is a person: someone reads the inbox, rewrites the request as a Linear issue, and later remembers, or forgets, to tell the user it shipped.
Linear is where the work gets done, so the feedback that never reaches it never gets done. The usual fix is a PM copying requests across by hand, which works until the week they are busy. Then a Zapier zap that creates an issue and loses track of it the moment the issue moves. Either way the two lists disagree. An issue gets marked Done and the feedback item stays open, so the user who asked never hears. A request gets resolved in the inbox and the issue created from it sits in the backlog for a sprint or two before someone notices it is stale. The tax is small each time and paid every day. A link that runs both ways, and carries the state with it, takes the copying off the person in the middle. They still decide what becomes an issue.
How it works
Disclosure: I build Usero, so weigh that. You connect Linear with OAuth from the Linear card on your Integrations page and pick one team for the project. That card is the whole control panel: the team, one sentence that sets the direction ("Sync both ways between Linear and Usero", with Linear to Usero only, Usero to Linear only, or Off as the other choices), a label filter, the synced count, and a short Recent list of what moved. Turning the sync on backfills the team's open issues into the inbox straight away, and new issues arrive through a webhook after that. In the other direction every feedback item gets a Create issue button that files a Linear issue in the team and links the two. Status follows both ways for every linked issue, imported or created: completing or cancelling an issue in Linear resolves its feedback, and resolving feedback in Usero moves the issue to Done. Comments do not sync. If GitHub is connected too, both can import, but only one tracker can have the Usero-to-tracker direction on, and Create issue goes there.
Turn the sync on and the open issues in your team land in the inbox, backfill included. Set a label filter to bring in only issues tagged "feedback" or "bug", or leave it empty for every open issue. Imported issues run through the same AI classification and cluster with widget, Slack, form, and email feedback, so a bug an engineer filed in Linear and the same bug a user reported through the widget become one theme with a count.
Every feedback item gets a Create issue button. Click it and Usero files an issue in your connected team and links it, so the engineer gets the request where they already work and the feedback item shows the issue and its state. The outbound half of the direction sentence can also create issues automatically, for every new feedback item or for bugs only, once the AI has classified it. The default is manual.
Complete or cancel an issue in Linear and the linked feedback resolves. Resolve feedback in Usero and the linked issue moves to Done. Works the same for an imported issue and one you created from feedback, so nobody reconciles the two lists by hand.
The Linear card holds the setup end to end: team, direction, labels, count, and a three-line Recent list of real events. Direction is a single choice: both ways, Linear to Usero only, Usero to Linear only, or off. Pick Linear to Usero only if you want issues in the inbox but do not want Usero writing to your workspace.
The honest objection
If every report comes from someone with a Linear seat, keep triaging in Linear and skip this. The reason to put an inbox in front is that Linear only hears from people who can file there. Users on your widget, in Slack, on a form, or in email cannot, so someone copies their words across and the count of how many asked is lost. With the sync on, that feedback becomes a Linear issue in one click, the engineer-filed issues cluster with the user reports, and completing on either side completes the other. Linear stays the place engineers talk, and comments never leave it. If you only want a tracker, you have one.
FAQ
Open the Linear card on your Integrations page, click Connect Linear, and approve the OAuth request in Linear. Then pick the team the project should sync with. One Linear team per Usero project.
Open issues in the connected team, filtered by the labels you pick. Turning the sync on backfills them immediately, and new issues arrive through a webhook after that. Leave the label filter empty to bring in every open issue in the team.
Yes, when the direction includes Usero to Linear. Resolving a feedback item moves its linked issue to Done, whether the issue was imported or created from that feedback. Completing or cancelling an issue in Linear resolves the feedback the same way.
Both can be connected on the same project, and both can import issues into the inbox. Only one tracker can have the Usero-to-tracker direction on at a time, and Create issue goes to that one. Switching it on for Linear turns it off for GitHub, and the other way round.
Yes. Under the direction sentence, "Usero to Linear" is a choice: create issues manually, automatically for every new feedback item, or automatically for bugs only. Manual is the default. Automatic creation runs after the AI classifies the item, so the bugs-only option waits for that classification. Status sync for a created issue is automatic whichever option you pick.
No. The sync carries the issue and its state in both directions. Comments stay in Linear, and the feedback item keeps its own thread in Usero.
Not today. Issue sync works with GitHub and Linear. If your team is on Jira, tell us through the contact page and we will let you know when it lands.
Free tier. No credit card. Two-minute install. The AI opens the PR, you merge it.
Keep reading