Requests arrive from the widget on your site. Each one lands in your backlog with a status of Needs action, waiting for you to decide what to do with it.
The backlog view
Your project's main view shows all public requests (Request and Question categories), sorted by vote count and cumulative MRR. Each card shows:
- The request title
- Vote count and subscriber count
- Category (Request or Question)
- Current status
- Cumulative MRR from users who submitted or upvoted it (Pro and Business plans)
Private submissions (Error and Feedback categories) appear in the Inbox, not the public backlog.
The status pipeline
Each request moves through three statuses:
Needs action
The request has arrived but no decision has been made. This is the default for every new submission.
From Needs action you can:
- Move it to In progress when you decide to work on it.
- Move it to Completed to close it directly. For example, if it is a duplicate, already shipped, or out of scope.
In progress
Work is underway. Subscribers receive a notification when a request moves to In progress (requires email configuration on your project).
Completed
The request is resolved. Subscribers receive a completion notification.
Completed requests remain visible in the backlog with a resolved badge. They can be reopened (moved back to In progress or Needs action) if the issue resurfaces or the scope changes.
Changing a status
Open any request from the backlog. Use the status selector in the request header to pick the new status. The change saves immediately and triggers any subscriber notifications.
Internal notes
Each request has an internal note: a free-form text field visible only to dashboard users. Notes never appear in the widget or to end users. Use them for:
- Triage reasoning ("Deferring to Q4: affects 3 enterprise customers")
- Engineering context ("Needs a DB schema change, blocked on migration")
- Links to related issues or PRs
Internal notes are available on Pro and Business plans.
Request categories
The widget routes each submission into one of four categories, chosen by the user when they open the widget:
| Category | Dashboard label | Visibility | |---|---|---| | FEATURE | Request | Public backlog | | OTHER | Question | Public backlog | | ERROR | Error | Private inbox only | | FEEDBACK | Feedback | Private inbox only |
Request and Question submissions appear on the public-facing backlog where other users can upvote them. Error and Feedback submissions go directly to your private inbox and are only visible to dashboard users. Other users cannot see them or their vote counts.
Revenue weighting
With identity configured, the backlog sorts by cumulative MRR from all users who submitted or upvoted each request, not by raw vote count. A request from three $500/mo customers ranks above one with ten free-tier votes.
MRR is displayed per-request on the backlog card. It is sourced from the mrr or amount/interval fields in the identity token minted by your server.
To set up identity, see Identity and revenue weighting.
Searching and filtering
Use the search bar at the top of the backlog to filter by title. You can also filter by status or category using the controls above the list. Filters are not persisted between sessions.