Statuses
Define the lifecycle every post moves through — from "Under Review" to "Completed" — and customize the language and colors to match how your team actually works.
What Is a Status?
A status describes where a post is in its lifecycle. ProductBridge ships with sensible defaults like "Under Review," "Planned," "In Progress," and "Completed" — but you can rename, recolor, reorder, or add your own.
Statuses are organization-wide and shared across feedback and roadmap posts. You can hide specific statuses from specific surfaces (e.g., "In Progress" on roadmap only, "Open" on feedback only). Changelog posts don't use statuses — they have their own labels system, managed at Settings → Changelog.
Default Statuses
When you create a workspace, ProductBridge seeds a starter set of statuses:
| Status | Status Group | Meaning |
|---|---|---|
| Open | Open | Newly submitted, untouched |
| Under Review | Open | Acknowledged, being triaged |
| Planned | In Progress | Committed to be built |
| In Progress | In Progress | Actively being worked on |
| Completed | Completed | Shipped |
| Closed | Closed | Won't be built (won't do, duplicate, etc.) |
Status Groups
Every status belongs to one of four status groups: Open, In Progress, Completed, and Closed. Groups control high-level behavior — for example, the roadmap kanban columns are driven by status groups, and closed-group statuses are treated as terminal.
| Group | Statuses Typically In It |
|---|---|
| Open | Open, Under Review |
| In Progress | Planned, In Progress |
| Completed | Completed, Released |
| Closed | Closed, Won't Do, Duplicate |
On the Manage Statuses page, statuses are listed under their group headings, and each group has its own New button — a status is created directly into the group you add it from.
Manage Statuses
Open Statuses
Go to Settings → Statuses (the page is titled Manage Statuses).
Create or edit a status
Click New next to the group you want the status in. Each status has:
- Name — what users see (e.g., "Under Review")
- Color — used as a colored chip on the portal and in admin
- Show on Feedback Board — make available on feedback posts
- Show on Roadmap Board — make available on roadmap posts
One status carries a Default badge — it's applied to new posts automatically. The default can't currently be reassigned from the dashboard.
Reorder
Drag statuses to reorder them within their group. This affects the order they appear in the status dropdown.
Delete
You'll be asked to confirm before deletion. A status that's still assigned to posts can't be deleted — move those posts to a different status first.
Common Customizations
Different teams use different lifecycles. A few patterns we see:
Hiding Statuses From Specific Surfaces
Use Show on Feedback Board and Show on Roadmap Board to scope a status to where it makes sense:
- "Open" → typically feedback-only (roadmap items start as Planned)
- "In Progress" → typically roadmap-only (feedback rarely lives long enough to be "in progress")
- "Released" → may show on both feedback (closing the loop) and roadmap
Status Changes Trigger Notifications
Notifications for status changes are follower-based: everyone following a post gets notified when its status changes. Users follow a post via the bell icon on the post — and voting on a post follows it automatically. When you change a status, you choose whether to send with the Notify followers (email & in-app) toggle.
Status changes can also reach:
- Subscribed Slack/Discord channels
- Outbound webhooks
- Linked external systems (Jira, Linear, ClickUp) — if you've configured status sync rules
This is how you close the feedback loop — customers who voted for a feature get notified when it ships.
Pair every status change with a comment explaining the reason. "Planned for Q3 — bundling with the workspace redesign" is far more satisfying for customers than a silent status flip.