I would look to Automation to create something that can spot a change of priority and poke a value into a custom field. Or set priority based on a custom field.
But, I'd question the need for it. A described, this just feels like you're duplicating the priority field for no good reason other than you think you want a severity field. Could you tell us why you want to do this? Or is there a limited set of circumstances in which you want to do it (for example, if the user forgets to set a severity on creation, assume it based on priority)
Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events