Feature-request statuses

A feature-request board without statuses is a suggestion box. Statuses turn votes into a roadmap signal customers can see.

Bootstrapware Feedback uses a fixed set. There is no custom status taxonomy in v1, and there is no completed value, the shipped end state is shipped.

The five statuses

Status	Typical meaning
open	New submission. Default for creates.
planned	Accepted onto the roadmap; not started.
in_progress	Actively being built.
shipped	Released. Not `completed`.
declined	Won't do. still visible unless you archive elsewhere.

Lifecycle

open → planned → in_progress → shipped
  └──────────────→ declined

That path is conventional, not enforced by the API. You can move from open straight to shipped or declined. The widget filters by status; Hosted moderation changes status in the dashboard inbox.

For BYO, your backend stores status on each post and your admin UI drives transitions. The React package type is:

type FeedbackStatus =
  | "open"
  | "planned"
  | "in_progress"
  | "shipped"
  | "declined";

Webhooks on Hosted

When a Hosted post status changes, Feedback can emit feedback.status_changed. The payload includes board and post ids plus fromStatus / toStatus. Never include title or body.

Pitfalls

Mapping third-party "done" / "completed" labels to shipped in BYO. Do not invent a completed status string.
Hiding declined posts without telling customers why, often worse than a clear declined badge.
Expecting MCP to change status with post content, MCP configures boards only; moderation is dashboard (or your BYO admin).