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
| Step | Where | Why |
|---|---|---|
| 1. Create the release | Releases → New release | Version, build details and private metadata. The App Store and Google Play templates suggest fields. |
| 2. Link tickets | The Release field on each ticket | The release page lists every ticket in it. The board can filter by release. |
| 3. Test it | Testbench → Rounds, preset Release Candidate, linked to the release | Testers get the build and a survey. Their feedback stays with the round. |
| 4. Turn on the changelog | Project settings → Domain → Show the changelog | Your custom domain shows published release notes. |
How it runs day to day
- Plan the version: create the release and link tickets as you pick them.
- Filter the board by the release to see what is left.
- When the build is ready, run a Release Candidate round with your testers.
- Write the Release notes in plain language. Use
### New,### Improvedand### Fixedheadings to get tags on the changelog. - 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.
Related
Updated 2026-11-10. Owned by product.

