I am looking to see if there is a way to enforce a format for the Fix Version.

[David Whitlock]

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.

[Michael Andolfatto]

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:

1. Use the correct naming convention when creating versions
2. Teach anyone else they give the Project Admin permission to that they should also follow this convention

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.

• Project EX has 4 releases generated: EX.2022.Q1, EX.2022.Q2, etc.

It would then be up to the team to use these releases correctly