Field Priority should be modified during the transition not working in jira

[Gopikrishna_Kunduru]

I want priority value to be modified while creating the issue, for this i have created validator rule in create transition in workflow and added (Field Priority should be modified during the transition) , but when i tested this is not working. I have added screen to this transition as well.

Kindly assist how can i resolve this issue.

[Lisa Forstberg]

Hi @Gopikrishna_Kunduru ,

The priority field is one of the system fields in Jira. An issue will always have a priority, it can't be empty. The priority field also have a default value. 

So long as the Priority field is on the Create screen (the screen connected to the create issue action in the screen scheme) you will see it like above and it will have the default value.

You can change what values is in the list via Priority Schemes:

• Go to  settings > issues > Priority Schemes you find the schemes available in your site. Often many of the projects are using the same default priority scheme and we do not want to add values to the default scheme. 
• Create a project unique priority scheme and add what values you would like to have in your list
• Go to settings > issues > Priorities. Add a new priority and call it "Please choose" or "None"
• Go back to the priority schemes and ensure the "Please choose" or "None" - value is only present in your project unique priority scheme, not the
• Ensure that  the "Please choose" or "None" - value is the default value of your project unique priority scheme 
• Apply the new priority scheme to your project

Something like this:

But as @Marc - Devoteam  states here, validating on the create transition is the tricky thing. 

best regards

Lisa

[Gopikrishna_Kunduru]

Thanks Lisa, Can you assist how can i validate during create transition?

• In the validator on the create transition you validate that the Priority field does not have the "Please choose" or "None" - value

Regards,

Gopi

[Lisa Forstberg]

Yep I realised that we were talking about create transition :- D

I think the workaround might be to ignore the system field for Priority altogher and create a custom field. Custom fields can have empty values.

You can use the field required validator on the create transition for an empty custom field. See my example below field "Multilist" and the validator in the create transition

And if I instead set the "Multilist" custom field to required in the field configuration, this is how it looks on create screen

[Marc - Devoteam]

Hi @Gopikrishna_Kunduru 

This can't be done on the initial create transition, because the issue doe not exist.

The validator can only check if the priority field has a required value on creation, but not set it.

Create an automation rule that sets the priority based on creation of the issue.

[Gopikrishna_Kunduru]

Thanks for your response, Can we make priority as blank by default we want user to select the priority while creating the issue.

Pls advise.

[Marc - Devoteam]

HI @Gopikrishna_Kunduru 

Set the priority field on the create screen and create a field configuration, within the field configuration set the priority field as required.

Add this field configuration to the field configuration scheme and associate it with the issue types required.