Review and respond to feature requests
Turn customer suggestions into a clear product conversation.
Last updated 9 September 2026
On this page
Keep the original problem visible
Open Requests and read the title, description, comments, and available customer context. A request is evidence of a need; the suggested implementation is not always the only way to solve it.
Review the request
Check whether an existing request describes the same underlying problem.
Read votes and comments alongside the specific use case.
Choose an appropriate status as the request moves through review and planned work.
Add a clear developer response that explains what customers should expect next.
Review portal visibility and moderation controls before making the request public.
Handle duplicates deliberately
Merge only requests that are genuinely about the same need. A merge consolidates votes and follows into the chosen main request and hides duplicates. Preserve the useful context before merging. Similar wording alone is not enough when the requested behavior differs.
Close the loop
When a request becomes planned work, connect it to a roadmap item. When the work ships, update the relevant status and publish a changelog entry explaining the result. Status and response changes can notify followers according to the app’s settings, so write them as customer-facing updates rather than internal notes.