How to Set Up a Product Feedback Workflow in Linear

Linear is built for engineering teams. But with the right setup, it becomes a complete product feedback system. Here's how to configure your Linear workspace to handle customer feedback from submission to shipped feature.

Step 1: Create a Feedback Project

Create a dedicated Linear project for customer feedback. Name it something user-facing like "Feature Requests" or "Community Feedback" — this name may appear on your public board.

Set up workflow states that make sense publicly:

• Submitted — New requests, not yet reviewed
• Under Review — Your team is evaluating
• Planned — Committed for a future cycle
• In Progress — Actively being built
• Done — Shipped
• Won't Do — Declined with explanation

Step 2: Define Labels for Organization

Create labels that help both your team and your users:

• Feature — New capability requests
• Bug — Something broken
• Improvement — Enhancement to existing functionality
• Integration — Third-party connection request
• Public — Controls visibility on the public board

Use the "Public" label to mark which issues appear on your public board. Internal-only issues skip this label.

Step 3: Connect a Public Board

Connect your feedback project to a public board using OpenIssue. Filter to show only issues with the "Public" label in your feedback project. This gives you precise control over what users see.

Enable:

• Submissions — Users add requests that create Linear issues
• Voting — Users upvote to signal demand
• Email notifications — Users get updates on issues they follow

Step 4: Build a Triage Routine

New submissions need triage. Set up a weekly routine:

1. Review new "Submitted" issues
2. Add the "Public" label if appropriate
3. Add category labels (Feature, Bug, etc.)
4. Move to "Under Review" if it needs team discussion
5. Reply to the user with acknowledgment

Keep triage fast — 15 minutes per week is enough for most teams.

Step 5: Connect to Sprint Planning

During sprint planning, pull the top-voted issues from your feedback project. Vote data supplements your team's priorities — it doesn't replace them, but it ensures community demand is visible.

Step 6: Close the Loop

When a feedback issue ships:

1. Move it to "Done" in Linear — the public board updates
2. Voters receive email notifications
3. Write a changelog entry describing the improvement
4. Optionally, reply on the issue thanking the community

This loop is what turns a feedback workflow from "we collect requests" into "we ship what users need."