GitHub issues are for bugs and discussions, not for product decisions. Featurewall gives your open-source project a place where users request and vote on features, you maintain a public roadmap, and your changelog announces every release to subscribers.
Free plan · Set up in 3 minutes · Cancel anytime
If any of these sound familiar, a feedback board is the fix.
Feature requests, bug reports, and drive-by questions mix in one issue tracker — and triage drowns in duplicates.
An issue with 3 comments and an issue with 300 comments look identical in the tracker. Votes fix that.
New contributors ask "what should I work on?" — a public roadmap with statuses answers it.
Collect requests, let votes prioritize, and announce every shipment.
Users vote without a GitHub account, so demand from non-developers finally counts.
Show planned and in-progress work. Contributors pick up what matters, and users stop filing duplicates.
Announce releases to subscribers and RSS readers. Keep your community in the loop without a blog.
Put the board and changelog in your documentation, right where contributors already are.
A real board, with real requests and votes, rendered in under a second.
No — issues stay for bugs and discussions. Featurewall is the product layer: requests, votes, roadmap, and changelog, in a format non-developers can use.
Absolutely. Add the board and changelog links to your README, and let users self-serve instead of filing feature requests in the tracker.
Every post is moderated before it goes public, and there is a honeypot that traps bots on the submission form.
Create a free board, send the link to your five most vocal users, and watch the roadmap write itself.
Get my board link