/
The Jira Fix Version Lifecycle: How It Works

Try Advanced Release Planning for Jira Cloud free for 30 days

The Jira Fix Version Lifecycle: How It Works

This page is a neutral, factual reference for how Release Management, Roadmaps & Product Portfolio for Jira supports the full lifecycle of a Jira Fix Version — from creation through release — on a single planning surface. For the narrative version, see the linked blog post at the bottom.

What a Fix Version is

In Jira, a Fix Version (also called a version or release) represents a scope of work that ships together. Its job is to answer one question: in which release will this work ship? A version moves through three lifecycle states:

  • Unreleased — the version exists and is accumulating scope.

  • Released — the version has shipped; its scope is fixed and dated.

  • Archived — the version is retired and removed from active Fix Version dropdowns, so new work is not assigned to it by mistake.

The four stages of the lifecycle

1. Create

A version is created with a name and, optionally, start and release dates and a description. In standard Jira this is done in Project settings → Releases; in Release Management, Roadmaps & Product Portfolio it can be created inline on the planning surface.

2. Scope

Issues are associated with the version through the Fix Version field. Scope is expected to change as planning firms up. Keeping the Fix Version field itself authoritative — rather than a saved filter that can go stale — keeps the release view accurate.

3. Track

Progress is read from each issue's status and estimate. The app shows a burnup of completed versus remaining work and produces a probabilistic (Monte Carlo) forecast of the release date from the team's real throughput, so scope and confidence update together as work moves.

4. Release

When the version ships, it is marked Released. Issues that are not yet complete can be cascaded to a subsequent version, so the next release begins already carrying the outstanding scope. The released version can then be archived.

Why one surface matters

Standard Jira spreads these stages across separate surfaces (the Releases tab, the backlog, and dashboards). Because Release Management, Roadmaps & Product Portfolio reads and writes the same Jira issues, create, scope, track, and release all happen on one view, and the version's state stays consistent throughout.

Related