Move feedback through statuses
Use statuses to track each request from submission to shipped and keep customers informed.
On this page
More in Core Features
- Manage feedback boards
- Use the roadmap
- Publish changelog entries
- Embed the feedback widget in your app
- Branding and customization
- Guest and anonymous feedback
- Internal comments and team collaboration
- Collect feedback with boards
- Move feedback through statuses
- Voting and comments
- Merge duplicate feedback posts
- Private boards
- Identify signed-in users in the widget
- Widget configuration options
- Widget JavaScript API reference
Statuses let your team show the current state of every request, both internally and on the public portal.
How statuses work
You move a post through stages to reflect where it stands in your process. The sources show these example stages:
Review – the request has been received and is being assessed.
Planned – the team has decided to build it.
In Progress – work has started.
Shipped – the feature has been released.
Who controls statuses
Your team decides when to move a post from one status to the next. Customers do not change statuses themselves.
Why statuses matter for customers
When a post moves to Planned or Shipped, customers who submitted or voted on it can see that their feedback had an effect. This closes the loop between their request and your delivery.
Keeping the team in the loop
Status changes are visible to teammates in the workspace, so everyone on the product team can see what is moving forward without needing a separate update.
Was this helpful?