Moderation workflow

Day-to-day flow for processing inbound submissions: accept, decline, link to existing, route to a release.

The moderation queue is the inbox for everything submitted through your Feedback Hub or Public bug reporter. This page covers the moderator's day-to-day flow, what to do with submissions as they arrive.

Where the queue lives

In the project, navigate to Feedback Hub (gear icon → Feedback Hub). The Moderation tab lists every pending submission, newest first. Real-time delivery means new submissions show up at the top within ~100ms, no refresh needed.

Each submission shows: type (bug / feature / general), title, body preview, severity (for bugs), submitter email if provided, and submission timestamp.

Actions on a submission

Click a submission to expand the full body. You then have four actions:

  • Accept as task, opens the convert preview (Convert feedback to task) and creates a new typed task on confirmation.
  • Accept and link to existing task, for duplicates. Attaches the submission to an existing task as supporting context. Doesn't spawn a new task.
  • Decline, marks the submission as declined. Stays in the record. If you've enabled the "show declined responses on public hub" setting, the submitter sees the decline reason.
  • Defer, leaves the submission pending. Useful for "need to investigate before deciding".

Routing to a release

If the hub setting Auto-attach accepted items to active release is on, every accepted task lands on the project's current active release. If off, accepted tasks land with no release and you assign them via the task modal later.

For high-volume hubs, consider creating a "Triaged" release that accepted items land on by default, then re-route them to the right shipping release during a weekly review. See Releases.

Triage cadence

A reasonable rhythm for solo founders / small teams:

  • Real-time alerts: enable browser notifications so you get pinged on new submissions.
  • Daily quick triage: scan new submissions, accept obvious ones, defer the unclear, decline noise.
  • Weekly deeper triage: reconsider deferred submissions, look for patterns across recent feedback.

The queue is search/filter-poor in v1, you scroll through new items. For projects taking high submission volume, this is a known limitation; upgrades are on the roadmap.

Public response

When declining, you can attach a public response that the submitter sees. Use this for "won't fix because X" or "duplicate of Y" so users understand the decision instead of feeling ignored.

If you're not on Pro and want full custom-branded responses, the v1 response surface is plain text only.

Activity attribution

Every accept, decline, and link action records an entry in the Activity feed attributed to the moderator's account. This means later you can see who triaged what, useful for distributed teams.

What's next

Last updated