Feature request template, built around the problem.
Good feature requests describe the problem, not just the button. This template asks for who has the problem, what they do today and why it matters, so your team can decide what to build next. Copy it or download the Markdown file. It is free, no sign-up needed.
# Feature request: [Short title] Submitted by: [Name, company] Date: [Date] Customer segment or plan: [e.g. Pro, 50 seats] ## The problem [What are you trying to do, and what gets in the way today?] ## Who has this problem [Which users or teams, and how often it happens] ## Current workaround [What you do today instead, and what it costs you] ## Proposed solution (optional) [How you imagine it working. Describe the result, not only the button.] ## Impact How important is this? [Nice to have / Important / Blocking] What changes if it ships? [Time saved, revenue, fewer errors] ## Examples and attachments [Screenshots, links, examples from other tools] --- For the product team Status: [Under review / Planned / In progress / Shipped] Votes: [Count] Related requests: [Links] Decision and reason: [Notes]
Three habits that make it actually work.
Problem first, solution second.
The proposed solution is optional. The problem and the workaround tell you far more about what to build.
Ask for the impact.
“Nice to have” and “blocking” requests should not wait in the same queue. One question sorts them.
Close the loop.
Tell the person who asked when the status changes. People who hear back keep sending useful feedback.
Collect them on a Roadmarq board
- One board for ideas and votes. Feature requests with categories, statuses and clean IDs like FR-312. Anyone can vote without an account, de-duplicated and bot-protected.
- Close the loop automatically. Email updates on status changes and comments, a public roadmap, and a changelog with RSS.
- Your brand, your site. Per-board logo, cover and accent color, plus an embeddable widget for your board, roadmap or changelog.
Three tools, one subscription.
Every plan includes Dutify Cloud, Codexum and Roadmarq.
Feedback and roadmap
Feature requests, voting without an account, a public roadmap and changelog.
Projects and sprints
List, board, table, calendar and Gantt views, custom fields and automations.
Team wiki
Docs your team and your AI tools can search, with permissions per space and page.
Questions
What should a feature request include?
The problem, who has it and how often, the current workaround, the impact if it ships, and optionally a proposed solution with examples or screenshots.
How do I prioritize feature requests?
Group duplicates, then weigh how many people ask (votes), how much it matters to them (impact), and how well it fits your roadmap. A shared board makes the first two visible.
Do customers need an account to vote in Roadmarq?
No. Anyone can vote without an account, de-duplicated by a privacy-friendly fingerprint and bot-protected. Every board can have its own branding and an embeddable widget for your site.
Skip the blank page with Roadmarq
Start free and keep this structure next to the work it belongs to.