You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We are trying to enforce a Fix Version format in our org. Ideally, we would like to keep teams from putting whatever they want and use a fix version meaningful like W.2022.12.01, for example. Is there a way of carrying a rule out.
Hi @David Whitlock ,
Since you need to be either a Jira Admin or a Project Admin to create project versions, there is some level of governance that can be applied to naming conventions. Unfortunately, there is no real validation for this. Those who are designated as Project Admins would need to be trained to:
Depending on the release structure/cadence of your organization, maybe it would be possible to script a solution for this (again, no real validation other than manual) which would create X number of releases for each team to use based on something like the project key.
It would then be up to the team to use these releases correctly