How to Link Customer Feedback Themes to Linear Issues and Projects

A theme tells you where customers are talking; an opportunity says what is wrong and how much it matters. Write the problem as one sentence in customers' words, then size it on four numbers: unique accounts in the last 90 days, their combined ARR, severity, and trend.

Set a bar before anything reaches Linear, such as five or more accounts in 90 days, or one account that cited the problem in a churn or lost deal. Below the bar, opportunities stay in your feedback tool and keep collecting evidence. To rank the rest, see how to decide what to build next.

Write it in the format engineers will see at the top of the Linear project. Budget 15 to 20 minutes per opportunity if your evidence is already in one place.

## Problem
[One or two sentences in the customers' words]

## Evidence (as of [date])
- [n] accounts in the last 90 days · $[ARR] · trend: [rising / flat / falling]
- Severity: [blocks a core job / costly workaround / annoyance]
- "[Quote]" ([account], [source link])
- "[Quote]" ([account], [source link])
- "[Quote]" ([account], [source link])
- Full evidence: [link to the opportunity or theme]

## Success metric
[What should change in customer feedback] · check on [ship + 14 days] and [ship + 30 days]

## Out of scope
[Related requests this project will not solve]

Pick three quotes, not thirty: one that shows the job, one that shows the cost, and one from your most important segment. Engineers read three and skim thirty. If you can't write the success metric, the project is not ready for Linear.

Search Linear first. A second project for the same problem splits the customer count and the after-ship signal.

• Name the outcome, not the theme. "Large exports finish for admins" beats "Export improvements."
• Use both text fields. The problem sentence goes in the short description, which shows in list views; the full brief goes in the project overview.
• Link back to the evidence. Put the link in the overview so an engineer reaches the source quotes in one click.
• Split the work into issues. Give each issue only the quotes that apply to it.

Customer Requests ties customers to the work they asked for. Customers are organizations with fields such as revenue, size, tier, status, and owner, and requests attach to issues and projects (Linear docs). A project's Customers tab rolls up requests from its issues, and you can sort projects by customer count and revenue (Linear changelog).

• From support: Intercom, Zendesk, and Front create requests on Business and Enterprise. Linear Agent can turn an Intercom or Zendesk conversation into triaged issues linked to the customer in one click (Linear changelog).
• From sales: Gong creates requests from call transcripts on Enterprise, and Salesforce creates issues from cases as an Enterprise add-on (Linear Salesforce docs).
• From everywhere else: by hand, through the GraphQL API, from Slack, or from tools such as Plain, Pylon, and Attio (Linear integrations).

Two habits keep the data useful. Flag a request Important only when it blocks the customer, so the flag keeps its meaning, and sync revenue and tier from your CRM or support tool instead of typing them.

Linear Agent, on all plans, can also "extract common requirements across customer requests" to start a spec (Linear changelog). That covers requests already in Linear; themes across calls, interviews, and surveys still come from Step 1.

"Two-way sync" means something different in every tool, so decide ownership before you connect anything. When two tools can both edit status, they eventually disagree and nobody knows which is right.

Link both ways: one click from the Linear project to the evidence, and one from the opportunity to the Linear project. If you get only one direction, choose Linear to evidence. Anyone can find status in Linear; the evidence is what goes missing.

When the project completes, book two checks, 14 and 30 days after release. At each, count unique accounts raising the same theme in equal windows before and after, and sort the new quotes into "same problem," "new problem," or "unrelated."

Call it fewer, about the same, more, or too early to tell, and post the verdict as a Linear project update. The full method is in how to measure whether a release reduced customer complaints.

Tell customers when the work ships, but tell your team it worked only after the 30-day check. Linear can notify you when a customer's requested issues or projects ship if you subscribe from that customer's page (Linear changelog). For what to send, see how to close the customer feedback loop.