Release and version tracking
Work items can be assigned to named releases or versions, with release progress and release notes tracked in the tool.
On this pageWhat it is
What it is
Release tracking lets you group work into a named release, such as version 2.4 or the March update. You can see how much of the release is finished and what is still open, and some tools help you produce release notes from what shipped. Jira and Linear are examples of tools with this.
Why it matters
Anyone shipping a product on a schedule needs to know what is in the next release and whether it will be ready. Without it, status is pieced together from conversations and release notes are written from memory. You need this when you ship numbered versions, work with customers who ask what changed, or coordinate launches across teams. If you publish changes continuously and nobody asks about versions, it is less useful.
What to check
- Ask whether items can be moved between releases and what happens to unfinished work when a release closes.
- Check whether release notes can be generated or exported, and in what format.
- Test whether release progress is visible without opening each item.
- Find out whether releases can be linked to the code deployments that ship them.
Tools with Release and version tracking
Plan, track and ship software work with issues, boards and sprints for product and engineering teams.
Issue tracker and project management built for engineering and product teams shipping continuously.