Degraded performance We are experiencing technical difficulties at the moment. We will report back when have further details.
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.
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.
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
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs