Enforce/Validate a naming standard for Jira fixed versions while creating for Jira Projects

[Ravi Kanth]

Hello Team,

Currently we are following a specific format for naming Jira Versions while creating for jira projects. Is this possible to enforce/validate that naming format while creating Version for jira projects, entering improper naming format as Version name should restrict the user to add.

Naming formats for versioning the Jira Projects we follow are given below.

For monthly release version format-M.2020.03.30 (M.YYYY.MM.DD)

For weekly release version format-W.2020.03.30 (W.YYYY.MM.DD)

Please do the needful ASAP..

Thanks,

N.Ravikanth

[Kelly Arrey]

I would try creating an automation rule using the "version created" trigger and then an "advanced compare condition" to compare {{version.name}} to a regular expression and send an email or slack message if it doesn't meet the naming convention.

[Ravi Kanth]

Hi Kelly,

Thankyou so much for your reply, as per your above reply I could able to send the email on validating version name with regular expression if it doesn't meet the naming convention, but I could not able to restrict the version name it is getting added .

Could you please suggest me any solution to restrict without getting added when the version name doesn't meet the naming convention by displaying any notification message on the same page.

[Kelly Arrey]

Hi @Ravi Kanth Sorry, I don't know any way of restricting the creation of a version name. Hopefully some more expert members of the community can chime in.

[Kelly Arrey]

@Ravi Kanth Another approach would be to restrict the permission to create versions to a small group of Jira admins who know how to follow the naming convention, and make everyone else open a Jira ticket to ask them to create a new version.

[Debra Jones]

Also following - have similar problem myself. 

[Dave Mathijs]

Interesting question, following this topic.