Feature Request Tracking: Email vs Public Board

Most teams start by collecting feature requests through email, Slack, or support tickets. It works at first. Then it doesn't. Here's why a public board replaces email for feature request tracking—and how to make the switch.

The Email Problem

Email is private, unstructured, and scattered. When feature requests arrive through email:

• Duplicates pile up — Ten users request the same thing separately
• Context gets lost — Requests buried in threads, never aggregated
• No prioritization signal — You can't tell if one person wants something or a hundred do
• No visibility for users — They don't know if you've seen their request or if others want it too
• Manual tracking — Someone has to copy requests into your issue tracker

This doesn't scale. By the time you have 50 customers, email-based tracking is a bottleneck.

How a Public Board Solves This

A public board connected to Linear replaces the email workflow:

• One place for all requests — Users submit directly on the board
• Duplicates merge naturally — Users find existing requests and vote instead of submitting new ones
• Voting shows demand — You see which requests have the most support
• Users see status — They can check progress without emailing you
• Automatic Linear sync — Submissions create Linear issues, no manual copying

What About Private Requests?

Some feedback is sensitive. A user might report a bug specific to their account or request something they don't want competitors to see. That's fine — keep email open for those cases. The public board handles the 80% of requests that aren't sensitive.

Making the Switch

You don't have to migrate old emails. Start fresh:

1. Set up a public Linear board with submissions enabled
2. Link it from your app and support flows
3. When new requests arrive via email, point users to the board
4. Over time, email requests decline as users learn the new workflow

The Team Benefit

Your team stops being a message relay. Instead of reading emails, creating Linear issues, and replying with updates, the public board handles the flow. Users submit, vote, and get notified automatically. Your team focuses on building.