01
Create a single intake point
Every feature request lands in Submitted, whether it comes from support tickets, sales calls, or internal brainstorms. One column, one queue. No requests get lost in email threads.
// Feature Requests
Collect ideas, ship what matters.
From customer request to shipped feature in five columns. Every idea is tracked, reviewed, planned, and delivered. Nothing falls through the cracks.
Submitted
3Allow keyboard shortcuts for card actions
Enhancement
Add dark mode toggle to public share pages
Enhancement
Support recurring due dates on cards
EnhancementPriority
Under Review
2Bulk archive cards from board view
Enhancement
Custom fields on cards for metadata tracking
EnhancementDesign
Planned
2Email-to-card: create cards by sending email
EnhancementPriority
Board-level analytics dashboard
Enhancement
Building
1Drag cards between boards in multi-board view
EnhancementPriority
Shipped
2Add comment threading on cards
Shipped
Implement card cover images from attachments
Shipped
02
Review requests with context
Move promising requests to Under Review. Add comments with customer quotes, vote counts, and revenue impact. Decisions are better when the card carries the context, not the reviewer memory.
03
Plan with commitment
Cards in Planned have a clear scope, an owner, and a target cycle. If you cannot answer who is building it and when, the request stays in Under Review until those answers exist.
04
Close the loop when shipped
When a request ships, move it to Shipped and notify the customers who asked for it. Closing the feedback loop builds trust and turns requesters into advocates.
01 How do I collect feature requests from customers?
+
Use Flux card comments to capture customer quotes directly on request cards. Create cards from support conversations, sales notes, or in-app feedback forms. Each card becomes a living record of demand for that feature.
02 How do I prioritize feature requests?
+
Use labels for Priority and Design complexity. Add customer count and revenue impact in card descriptions. Review the Under Review column biweekly and promote high-impact, low-effort requests to Planned first.
03 Should product managers and engineers share the same feature request board?
+
Yes. Product owns the Submitted and Under Review columns. Engineering owns Building. Planned is the handoff point where both sides agree on scope. Shared visibility prevents misaligned expectations.
// Listen, build, ship
Every request, tracked.
No credit card. Free feature tracking with labels, comments, and real-time sync.