nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is it possible to 'lock' a version? (prevent selecting version)

Lucas Molenaar

Is it possible to 'lock' a version so no other issues can set the 'fix version' to that version? Basicly preventing that the scope of the version will change from that moment onwards.

Prefferably by a post-transition step. if not supported ideas/suggestions how to achieve this are also welcome.

Accepted answers

Jobin Kuruvilla [Adaptavist]

If you are looking to lock a version for new issues while keeping it active for existing issues, it is not possible right now. Since the versions are used in many places, that will need core code changes.

Archiving, as Christian mentioned, can work if you want to make it offline totally.

All comments

Christian Czaia [Decadis AG]

You can archive a version:

https://confluence.atlassian.com/display/JIRA/Managing+Versions#ManagingVersions-Archiveaversion

Cheers

Christian

Jobin Kuruvilla [Adaptavist]

Archiving, as Christian mentioned, can work if you want to make it offline totally.

Lucas Molenaar

Thanks both! Could somebody advise how to archive a version during a transition (post function)?

Yen Pham_12lzeh

This seems to be the closest solution; the issue assigned to the archived fix version cannot have its fix version edited unless you unarchive the fix version.

However, archiving a fix version will make the version disappear from your scrum board even if you go to board settings -> card layout, and add "Fix Versions/s" in the backlog view

Here's the original feature request

https://jira.atlassian.com/browse/JRASERVER-5162

James Tuttle

Archiving is a good suggestion, thanks!

It does prevent people from manually selecting the archive Version as the fixVersion. However, if you have an epic (even a closed epic) that has the archived Version as its fixVersion, and hit the "+" (Create Issue in Epic), the new issue will inherit that fixVersion.

So, archiving is not a foolproof way to prevent issues getting added to released Versions...

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

version