Should "fix version" be renamed to "release"?

Question

It is a bit confusing when the same thing has two different names.

In most cases we are not fixing anything, we just want to release a new thing.

"fix version" sounds like a legacy thing back when Jira was for SW development only.

What do you guys think? Should we make a suggestion for a rename, or at least an option to change the name?

Tomislav Tobijas · Answer

I actually agree that "Release" (or just "Version") would be more intuitive, especially for teams using Jira beyond software development. 🙂

Personally, I'd prefer an option to customize the field's display name rather than renaming it globally, while keeping the underlying functionality and JQL references unchanged.

I know it's sometimes a bit hard to explain to people who haven't used Jira before and say something like, "We're here talking about Releases, but the system uses native 'Fix versions' field to actually link the work item with the release…" 🤦

And apart from 21293, there's also this one JRACLOUD-94497: Ability to Rename or Delete Locked System Fields in JIra Cloud but I feel like these two could merge.

Cheers,

Tobi

Cloverkite · Answer

Hello @Michal Koziel

Agreed. Jira is already halfway there: the project page for versions is called Releases (left sidebar), while the field and JQL still say Fix versions / fixVersion.

Until JRACLOUD-21293 moves, two small things make it less confusing:

* Name the versions like releases (e.g. “2026.11 - Checkout”), so the field reads naturally on an issue: Fix versions: 2026.11 - Checkout.
* Add the field’s meaning to your board or project description: “Fix version = the release this ships in”. New team members stop asking.

And yes, voting on JRACLOUD-21293 is the way to push for a real rename.

Michal Koziel · Answer

Thanks! I will check this out.

Gathering interest since 2016. Sound like good old Atlassian :-)

Cheers!