There is no way to do this natively, I'm afraid.
You could try injecting javascript to try to stop people using non-numeric characters, but you may need to make it work in many places, and javascript is notoriously hard to make work in Jira and hard to maintain or upgrade.
Thank you for your reply.
Is it possible to solve this problem with Bamboo integration (release naming using variables) or try some plugins?
https://confluence.atlassian.com/bamboo/naming-versions-for-deployment-releases-361726798.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You could use Bamboo with a good naming scheme so that users aren't tempted, but it won't stop them adding their own with letters in them.
Another thought sprang to mind for me - if you're willing to code (or use ScriptRunner), you could write a listener that picks up "version created" events, and does something with them. My initial idea would be "remove all non-numeric characters and check it's not now a duplicate, removing the version if it is, and renaming it if it's new", but you'd have to explain that carefully to your users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for detailed consultation
Can I use webhook for these purposes also ( like a trigger on "version created")?
https://developer.atlassian.com/server/jira/platform/webhooks/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've not tried webhooks on events other than issue events.
I suspect you can.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.