Statuses
Statuses track where a post sits in your workflow. Rename, recolor, and reorder them, and map your statuses to the three public roadmap buckets in Feedjolt.
A status is the state a post is in: "Under review", "Planned", "Shipped", whatever your team uses.
Defaults
A new workspace ships with five statuses:
- Open - the default for new submissions. Not on the roadmap.
- Under Review - being triaged. Not on the roadmap.
- Planned - committed, on the roadmap, not started yet.
- In Progress - actively being built.
- Complete - done.
You can rename, recolor, reorder, or delete any of these.
Custom statuses
Dashboard -> Settings -> Statuses. For each status:
- Name - short, action-oriented. "Researching" beats "TBD".
- Color - used in the dashboard and portal.
- Sort order - controls the column order on the dashboard roadmap.
- Show on roadmap - toggle. Only statuses with this on appear as columns on the dashboard roadmap.
- Public bucket -
Planned,In Progress,Done, orHidden. Controls which column (if any) the status maps to on the public portal roadmap. - Default - exactly one status is the default for new posts.
Dashboard roadmap vs public roadmap
Two views, two controls:
- The dashboard roadmap has one column per status with
Show on roadmapon, ordered by sort order. Optimised for member triage. - The public roadmap always has exactly three columns - Planned, In Progress, Done - and groups your statuses into those buckets via the
Public bucketfield. A status with no bucket assigned never appears on the public roadmap.
That separation lets you keep a fine-grained internal workflow (Researching, Up next, Beta, GA) while showing customers a simple three-step story. Configure the mapping at Dashboard -> Portal -> Public roadmap.
Workflow rules
We don't enforce status transitions. You can move a post from "Shipped" back to "Under review" if you need to. Power-tool, sharp edges; we trust you.
If you want guardrails, a future "workflow rules" feature is on the roadmap. Until then, train your triage team.
What changing a status does
Changing a status:
- Records a status change event with who, when, from -> to.
- Triggers notifications: email to the post author and subscribers; Slack message if the workspace has a channel mapping for
status.changed. - Moves the post on the dashboard roadmap (if "Show on roadmap" is on for both old and new status) and on the public roadmap (if both statuses have a public bucket assigned).
- Optionally publishes a changelog entry - for status changes to a "Done"-bucket status, you can promote the post to a changelog entry in one click.
Status history
Every status change is logged. Open a post in the dashboard and click History to see the full timeline (post created -> status changed -> ...).
This data is API-accessible via the public API.
Posts
A post is a single piece of feedback in Feedjolt: title, body, status, tags, votes, and comments. Learn how posts are submitted, edited, merged, and moved.
Voting
How voting works in Feedjolt: one vote per user per post, toggle to add or remove, who can vote per board, vote-on-behalf, thresholds and anonymous voting.
