Browse all guides

Ship a release with public release notes

For: product teams who release on a schedule and want customers to see what changed. You get: each ticket tied to a version, a test round on the release candidate, and a public changelog on your own domain.

The setup

StepWhereWhy
1. Create the releaseReleases → New releaseVersion, build details and private metadata. The App Store and Google Play templates suggest fields.
2. Link ticketsThe Release field on each ticketThe release page lists every ticket in it. The board can filter by release.
3. Test itTestbench → Rounds, preset Release Candidate, linked to the releaseTesters get the build and a survey. Their feedback stays with the round.
4. Turn on the changelogProject settings → Domain → Show the changelogYour custom domain shows published release notes.

How it runs day to day

  1. Plan the version: create the release and link tickets as you pick them.
  2. Filter the board by the release to see what is left.
  3. When the build is ready, run a Release Candidate round with your testers.
  4. Write the Release notes in plain language. Use ### New, ### Improved and ### Fixed headings to get tags on the changelog.
  5. Set the release to Published and tick Show on the public changelog.

Tips

  • An agent can draft release notes from the linked tickets. Only a person can put them on the public changelog. If an agent edits the notes, title or version of a published release, the release leaves the changelog until a person publishes it again.
  • Release metadata stays private. Only the version, title, notes and date are public.
  • Keep one release per store build, so test feedback and fixes line up.

Updated 2026-11-10. Owned by product.