Why release notes get skipped
On release day the work is done, but someone still has to go back through the board, find what shipped, look up each issue number and write it up for the team, the client or the support channel. It's tedious, so it gets rushed - or skipped.
In Raidzo the list already exists: it's your sprint. You only choose what's going out, and Raidzo writes the notes.
How it works
- 1Turn on Release notes in the project's Settings → General.
- 2Open Releases and click New release - give it a name like 1.4.0 and a date.
- 3Pick a sprint (the newest is first) and tick the items going out. Select done ticks only the finished ones.
- 4Add anything from outside the sprint with the search box, write a short note, and click Publish.
- 5Click Copy and paste the notes into your team chat, email or changelog.
What you get when you click Copy
Plain text that pastes cleanly anywhere - for example:
| Line | What it shows |
|---|---|
| Hello everyone, version 1.4.0 was released today. | The release name and day |
| 1. CSV export for reports [APP-43] | Each feature, numbered, with its issue key |
| 2. Dark mode [APP-47, APP-48] | Subtasks that shipped with it share the line |
| 3. Bug Fixes: | Bugs are grouped together at the end |
| a. Login redirect loop [APP-42] | Each fix, lettered, with its issue key |
Built for teams that ship often
Straight from the sprint
The release starts from the sprint you pick, so there's nothing to retype.
Issue keys included
Every line carries its key, like APP-42, so anyone can find the work behind it.
No double counting
Items already in an earlier release don't show up again - releasing several times in one sprint just works.
A history of releases
Every published release stays on the Releases page with its date, items and notes.
Frequently asked questions
Is there a free release notes generator for small teams?
Yes - release notes are included in Raidzo's free plan, which covers up to 5 users with every feature. Larger teams pay ₹149 per user per month for users beyond the first 5.
Can I generate release notes from a sprint?
Yes. Pick the sprint, tick the items that shipped (or click Select done for just the finished ones), publish, and copy the notes.
How are bug fixes shown?
Items whose type is a bug are grouped under a Bug Fixes heading at the end, so the new features come first.
Can it write release notes from Git commits?
Not yet - Raidzo has no Git integration. The notes are built from the work items you tick, and each line carries its issue key so it's easy to match with commits and pull requests.
Try it on your next project
Set up your organization in a couple of minutes. Free for up to 5 users, with every feature included.
Prefer a walkthrough? We'll show you Raidzo on a 20-minute call. See pricing