Can you force users to select a Priorty?


we want to force the users to make a decision about the priority of an issue. currently I can not see a way of achieving this without replacing the field as a custom field. 



6 answers

3 votes

Change the "field configuration" for the issues - make priority mandatory.

Since there's a default value, you would have to make a workflow validator on the create transition that checks if the value of Priority has changed. That would mean you can't use the default Normal value though, since it's going to force you to change it.

To remediate that, you could create a priority called "No Priority" or something like that, and make that the default value.

I'm not 100% sure you can use that validator with only JIRA out of the box, so you may have to get the Misc. Workflow Extensions add-on. But it's worth the price.

Hi Michael,

Using JJUPIN plugin you can very easy put conditions on JIRA's fields.
For example, let's say you don't want to allow users to create issues with priority different from "Major". All you have to do is to create a validator on the create transition from your workflow. It should look like this: 

if(priority != "Major") {
   return false, "priority", "Priority must be Major!";

The result would be: 



Hope this heps,

Hello Michael!

You don't need to have a custom field to set it as mandatory, you can set a default field in JIRA as required as per the Making a field required or optional section in the link

But notice that, if you modify the field behavior in the Fields Configurations, all the projects which use the project will be affected with the required behavior.



HI all,

Sorry I wasn't very clear. I have already set the field to mandatory but I want to force the users to select a priority rather than it defaulting to an any value.




Hi Michael,

This is very simple to do using JJUPIN. We have Live Fields (you can read more about it on our documentation page: integrated, so all you have to do is write a few lines. 

For your problem, you will need a custom field in which you will retain if the priority has been changed, two scripts of one line each and a short validator on the "create" transition. Let me  show you:

The first script would look like this:

lfWatch("priority", "priority", "hook.sil");

The second script ("hook.sil"): 

lfSet("prioritySet", "true");

And the validator: 

if(prioritySet != "true") {
   return false, "prioritySet", "Priority hasn't been set!";

This way, an user won't be able to create an issue if he doesn't change the priority.


Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,774 views 11 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot