How to get there: Posts are managed from All Posts in the sidebar. Statuses and boards are configured in Settings → Boards (separate page).
ProductLift is built around a simple but powerful idea: a post can travel through your entire product workflow, from initial feedback to shipped feature to documentation, while keeping all its history intact.
When a user submits feedback, that post doesn't have to stay in one place forever. You can move it through stages as it progresses:
Feedback → Roadmap → Changelog → Knowledge base
The key difference from other tools: it's the same post throughout. The votes, comments, and discussion follow along. Users who voted on an idea in January automatically get notified when it ships in June because they're still following the same post.
Every post has a unique ID that stays with it regardless of which board it's in. This means you never lose context, and you never have to copy content from one place to another.
Boards are the main stages where posts live. The defaults are:
You can customize these however you like: rename them, add new ones, create multiple versions (like separate roadmaps for different products), or remove ones you don't need.
Each board has its own set of statuses that show progress within that stage.
Feedback statuses:
Roadmap statuses:
Changelog statuses:
Knowledge base statuses:
You can create your own statuses, and you can even create statuses that aren't linked to any board (useful for internal tracking or special workflows).
These work across all boards to help you organize by type:
When you're ready to move a post to the next stage, use the "Move Post" option. You'll see:
That's it. The post moves, keeps its history, and followers stay connected.
When a post reaches your Changelog, you probably want to write something more polished than the original feedback request. ProductLift lets you add a special changelog comment that becomes the public-facing announcement.
You can write this yourself or generate it with AI based on the post's history. The AI takes into account the original request, the discussion, and what was built.
Sometimes you ship a big update that addresses several feedback items at once. Here's how to handle that:
Everyone who voted on any of the linked items gets notified about the release. All the context from those separate discussions stays connected to the announcement.
After you've shipped a feature and announced it, you might want to document it. ProductLift can generate a knowledge base article from your changelog post using AI.
This completes the full lifecycle: an idea that started as user feedback becomes a roadmap item, then a shipped feature announcement, then permanent documentation—all connected, all traceable back to where it started.
The journey model is the default, but ProductLift doesn't force any particular workflow:
The system adapts to how you work, not the other way around.
| Concept | What it does |
|---|---|
| Boards | Main stages (Feedback, Roadmap, Changelog, Knowledge base) |
| Statuses | Progress within a board (e.g., "In progress", "Next") |
| Categories | Types of posts across all boards (e.g., "Feature", "Bug") |
| Tags | Flexible labels for filtering |
| Post ID | Unique identifier that stays with a post through all moves |
| Changelog comment | Polished announcement added when a post reaches Changelog |
| Linked posts | Connect related items (useful for combined releases) |