How do I set the Priority field as required only for a bug issuetype

[Dave CROWLEY]

We use Priority for classifying bugs and want to set priority as a required field only for bugs when the issue is created. I have already created an additional priority option to use for the other issues types (set as default option).

I looked at the workflow and was hoping to set some condition check on the Open step to check if the issuetype is bug, alert user to set the priority other than the default. I didn't see any option to do this check.

I was looking at https://community.atlassian.com/t5/Jira-Service-Management/Forcing-an-Agent-to-Choose-Priority/qaq-p/1979635 to fake the system, but there are a lot of moving pieces.

Any other options to make this work?

thx

Dave

[Mark Segall]

Hi @Dave CROWLEY and welcome to the community!

There are two options:

1. Field Configuration: You can create a specific field configuration for Bugs and set the Priority field as required then update the project's Field Configuration Scheme to assign the new field configuration to the Bug Issue Type.  Advantage to this solution is that the user will see the visual indicator that it is a required field and that will hold true regardless of where the issue is in the workflow.
2. Workflow Validator on the Create Transition:  You would use the Field Required validator on the Create Transition (the line between the circle and your Open status).  The advantage of this is that you can create a custom error message.  The downsides are that this only applies to creation (someone can clear the Priority field later) and the user will not see a visual indicator before they click "Create"

[Dave CROWLEY]

Thx Mark. I'll see if one of these will work for us, otherwise i'll try your suggestion my original question.