Feedback & Insights

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 customers.

Roadmap

Statuses

Every roadmap item has one of these statuses:

StatusMeaning
Under reviewReceived and being evaluated. Not yet committed.
PlannedCommitted to the roadmap. Not yet in development.
In progressActively being built.
CompletedShipped. Moving an item here has your agent draft a release note for the changelog.
DeclinedWill not be built. Declined items leave the board for the Declined list below it.

The board shows the first four as columns. The Declined list is folded under the board, with its count; open it to see those items and Reopen any of them (they go back to Under review).

Creating a roadmap item

Roadmap items can be created in two ways:

From a theme (recommended) — see AI Clustering.

Manually:

Go to Feedback → Roadmap.

Click New item.

Enter a title and description, then set the type, status and priority.

Optionally set an expected date, tags and whether the item shows on the public board, then click Add to roadmap.

Managing roadmap items

On the roadmap board you can:

  • Drag between columns to change status
  • Drag within a column to set the order (the public roadmap uses the same order)
  • Open an item (click its title) to edit it in a side panel: title, description, type, status, priority, expected date, tags, and Show on the public board
  • See the tickets and themes linked to an item in the same panel
  • Create ticket from any item, whatever its status. An item still under review moves to Planned; the others keep their status.
  • Delete an item from its panel. Linked themes and tickets stay, without the link; votes on the item are deleted.

Each card shows the item's type, priority, votes, feedback count, linked tickets and expected date. Items hidden from the public board carry a Private chip.

The public roadmap shows public items from Planned onward. Items under review, declined items and private items stay on your team's board only.


Changelog

The changelog is where you publish release notes. Each note can be linked to one or more completed roadmap items. Notes sit on a timeline, newest first; the All, Drafts and Published tabs filter it.

Creating a release note

Go to Feedback → Changelog.

Click New release note.

Write your release note in Markdown. Switch to Preview to see how it reads.

Optionally tick completed roadmap items under Link completed items. Add to the note appends them to the body as a list.

Click Publish to make it live, or Save draft to review later.

Release note fields

FieldDescription
TitleShort headline for the release (e.g., "CSV Export is here")
VersionOptional version label (e.g., 2.5.0)
TypeFeature, Improvement, Fix or Breaking change
SummaryOne line shown under the title
Release noteThe full note in Markdown
Linked itemsCompleted roadmap items this release ships. When you edit a note, the items already linked to it are listed and can be unticked.

AI drafts

When you move a roadmap item to Completed, your agent drafts a release note from the completed items no note covers yet. Draft with AI asks for one at any time. AI drafts carry an AI draft chip; edit them like any other note before you publish.

Drafts, publishing and unpublishing

Drafts are visible only to your team in the dashboard. They do not appear on the public board until published. Publish a draft from the timeline or from the editor.

A published note can be unpublished from its menu: it leaves the public changelog and becomes a draft again. Delete removes a note for good; its roadmap items stay completed and can go into another note.

Writing good release notes

  • Lead with the customer 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 customers who asked for it. It closes the loop and builds goodwill.

On this page