Open changelog management
Open the portal’s Changelog management screen. Completed feedback that has not yet been included in a release is available for selection. Create Release asks you which completed items to include.
Moving feedback to Completed, including from Kanban, may offer to continue into the changelog workflow. Marking something complete does not by itself mean a public release note has been published.
Choose where the items belong
After selecting the completed items, the Add to Changelog dialog offers:
- Create new release: start another changelog entry.
- Add to existing draft: add the selected items to the most recent draft release.
- Add to published changelog: add them to the most recent published release.
These shortcuts choose the most recent entry of the selected kind; they are not a picker for any historical release. If there is no draft or published entry of that kind, the app falls back to creating a new release and tells you what happened.
Adding items to a published changelog changes an entry customers can already see. Review the selected items and release before confirming.
Review and publish
Check the release title, version, description and included feedback. If you use the AI writing controls, read and edit the draft against what was actually delivered.
Keep a release as a draft while it is being prepared. Use the publish control when it is ready for users, and the unpublish control if it needs to be taken out of the published list. Adding completed work, saving a draft and publishing are separate actions.
Keep roadmap and feedback records consistent
A request can be linked to roadmap work and later included in a release. Read any status-synchronisation prompts when updating linked items so that you do not change related records unintentionally.
Manage roadmap items or update statuses on the Kanban board.