How to Track Feature Requests in Linear (Step-by-Step)
Linear's triage inbox and label system make it a capable feature request management tool for teams that want to avoid adding a separate tool like Canny or Productboard. When feature requests come from internal sources — sales, customer success, support — tracking them directly in Linear keeps all product work in one place and makes the path from request to ticket seamless.
This guide covers setting up a feature request tracking system in Linear using triage, labels, and project management features.
Step-by-step guide
Enable triage for your team
In Linear, go to Team Settings > Triage and enable the Triage feature. Set the "Default state for new issues from external sources" to Triage. Create a dedicated team or label called "Customer Requests" to separate product issues from engineering tickets. The Triage inbox becomes the PM's daily feature request queue.
Create a feature request label set
In Team Settings > Labels, create labels: "Feature Request," "Customer Request," "Internal Request," "Research Required," and "Won't Fix." Add a secondary label set for request source: "Sales," "Support," "User Research," "Internal." Two-label systems (type + source) enable filtering that a single label cannot.
Set up a feature request template
Create an issue template for feature requests: Title format: "[Company Name] - Feature Request - [Feature Area]." Body template: Customer (company name and size), Problem they described, Workaround they are using, Priority to them (High/Medium/Low), and Link to call notes or Slack conversation. This template ensures every request has the same information for prioritization.
Implement customer tagging
Linear does not have native customer tagging, but you can model it with a text custom field called "Customer." Add the company name. Filter the backlog by Customer field to see all requests from one company. For MRR-weighted prioritization, add an "ARR" number field. Sort requests by ARR to see which customer segment is most vocal about a feature.
Triage new requests weekly
Set a weekly 30-minute triage ritual: open the Triage inbox, review each new request, apply labels, fill in the customer field, and set priority (Urgent/High/Medium/No Priority). Close or Won't Fix requests that are clearly out of scope with a comment explaining why. Move high-priority requests to the team backlog.
Convert prioritized requests to roadmap projects
When a feature request reaches prioritization threshold (multiple enterprise customers requesting the same feature, or high strategic alignment), create a Linear Project from the request: open the issue > create a linked project. Add engineering issues as child issues in the project. Archive the original feature request issue, linking it to the project for traceability.
Close the loop with requesters
When a feature request is shipped, update the original Linear issue status to Done and add a comment: "This shipped in [version/date]. Here is the changelog entry: [URL]." If the requester is internal (sales, support), post in the relevant Slack channel. Closing the loop builds credibility and encourages future request submissions.
Common mistakes
Mixing feature requests with engineering tickets
Feature requests and engineering tickets in the same backlog create noise for engineers during sprint planning. Use a dedicated team or project for feature requests, separate from active sprint teams.
Not closing Won't Fix requests with explanation
Declining a feature request without explanation creates frustration for the internal teams that submitted it. A brief "Won't Fix" comment explaining the rationale respects the submitter's effort.
Treating all requests equally regardless of customer size
Five SMB customers requesting a feature has different weight than one enterprise customer. Use the ARR or customer segment field to weight requests and surface the ones with the highest business impact.
Tips
Create a shared Slack workflow that lets customer success submit feature requests directly to Linear Triage via a Slack form
Use Linear's "Related issues" feature to link multiple customer request issues to one master feature issue — shows total request count
Add a monthly "Feature Request Digest" to your team newsletter: top 5 requested features and their current status
Use Linear Analytics to track how long feature requests sit in Triage before being processed — this is a PM responsiveness metric
How Vantage helps
When prioritized feature requests graduate to full features, Vantage generates the PRD and tickets. Add the Linear feature request issue link as context in a Vantage project and Vantage incorporates the customer problem description and use cases into the PRD generation.