Roadmap & Changelog
Manage roadmap items through their full lifecycle and publish release notes to your changelog.
The roadmap tracks feature requests from discovery to delivery. The changelog lets you publish release notes tied to completed work and share them with users.
Roadmap
Statuses
Every roadmap item has one of these statuses:
| Status | Meaning |
|---|---|
under_review | Received and being evaluated. Not yet committed. |
planned | Committed to the roadmap. Not yet in development. |
in_progress | Actively being built. |
completed | Shipped. Should have a linked changelog entry. |
declined | Will not be built. Include a reason to close the loop with users. |
Creating a roadmap item
Roadmap items can be created in two ways:
From a cluster (recommended) — see AI Clustering.
Manually:
Go to Feedback → Roadmap.
Click New Item.
Enter a title, description, and set the initial status.
Optionally set priority and expected delivery date, then click Save.
Managing roadmap items
From the roadmap board or list view you can:
- Drag between columns to change status (board view)
- Inline-edit title and description
- Set priority —
low,medium,high,critical - Add internal notes — visible only to your team, not on the public board
- Link related items — connect related feature requests that may ship together
Declining a feature request
When declining, add a reason. The reason is optional for internal use but helps with team context. If the item is linked to a cluster, users who submitted that feedback can optionally be notified via the public board that this won't be built.
Changelog
The changelog is where you publish release notes. Each entry can be linked to one or more completed roadmap items.
Creating a changelog entry
Go to Feedback → Changelog.
Click New Entry.
Write your release note. The editor supports Markdown.
Optionally link completed roadmap items using the Link roadmap items field.
Set the publish date (defaults to today) and click Publish to make it live, or Save draft to review later.
Entry fields
| Field | Description |
|---|---|
| Title | Short headline for the release (e.g., "CSV Export is here") |
| Body | Full release note in Markdown |
| Linked roadmap items | Feature requests that this release resolves |
| Publish date | Date shown on the public board (can be backdated) |
| Status | draft or published |
Writing good release notes
- Lead with the user benefit, not the technical change. "You can now export conversations to CSV" beats "Added CSV export endpoint."
- Keep it short. A few sentences is usually enough. Use bullet points for multi-feature releases.
- Link to documentation where applicable.
- Thank users who submitted the underlying feedback — it closes the loop and builds goodwill.
Drafts
Saved drafts are visible only to your team in the dashboard. They do not appear on the public board until published. Use drafts to prepare release notes in advance of a ship date.
Notifications
When a roadmap item status changes to completed and a changelog entry is published, you can optionally notify users who submitted related feedback. This is configured per-entry in the changelog editor under Notify users.
Notifications are only sent to users who submitted feedback with an email address attached.