I see defaulting to a level causing issues where we skip the triage step and everything is Medium whether or not that is appropriate. I would appreciate the option to default to null for projects with a triage process that relies on the accuracy of the priority field.

yes please, definitely need this feature. 

How do you block a priority value from being selected, thus forcing the user to pick another one?

https://getsupport.atlassian.com/browse/PS-121341

Not enough votes on the ticket, I guess?  

How is this not solved yet!?

I'm sad this still happens in various situations. I guess I'll have to make a "No Priority" priority and block folks from being able to make tickets with that priority. 🙈

With Jira today, there is literally a setting on priority schemes to say this scheme has no default, but it doesn't actually work.  This is no longer actually a suggestion request.  It is actually a broken feature in Jira.

This request will have its 15th birthday next year.  For a company that talks about trying to empower teams, it seems allowing a configuration where issues have to be given a user considered priority vs just getting a default and every issue and up the same (because people can't be forced to make a selection) is totally opposite what you claim to be providing to your users.

But this is the typical crappy consideration your users are accustomed to I guess.

Just wondering, how many votes are needed for this, to qualify Atlassian's feature/fix request.

A disappointing outcome. We have teams requesting this feature, but will now have to advise them that it will not be provided and they should consider alternative ways of working to accommodate.

If people not only complained but actually stopped using and buying their stuff, things would change. You continue using it, must be good enough for ya

This was created 09/Jul/2007 1:35 PM. So far no solutions. I'm giving up on it.

Hi here,

This issue is also relevant for other "native" fields on Jira CLOUD. And from what I know there is no existing workaround for Jira CLOUD as priority schemes do not exist at all for CLOUD

Have good day

Clement

I agree with the above comment. It would be useful to have an empty Priority field be allowed as the default value. Until then, the workaround I proposed serves the purpose for us.

IMHO, the above is not resolving the root cause, it is indeed a workaround and the value is not actually empty but with a string call "Not prioritised" or "none", with Jira itself setting the priority value to empty, it will then recognise it as empty value and force use to consciously select the actual priority instead. 

Hi all,

A solution that I implemented as a global Jira admin for a project team was the following:

1. Add new priority (with name "Not prioritized", description "Issue not prioritized by user", and icon URL [a black question mark with white background]).
2. Add a new priority scheme (with name "Priority scheme - not prioritized default").
3. Add a new priority (called it "Not prioritized").
4. Make the new priority the default priority.
5. Associate the new Priority scheme with the project of the team that asked for it.

While Jira doesn't let you set unique priority schemes per issue type (e.g. one for Project X Stories and another one for Project X Bugs), you arguably don't need the Priority field to show on the screens of all the issue types in the project.
 

In my case, majority of our ticket priority is set to Medium by default which is useless and frustrating, there were workaround but manual tasks, it has been really hard and not viable to keep reminding people to amend their ticket priority accordingly. By having an additional empty value with option to set it as default, sounds very much a simple effort to implement with great outcome, hope Atlassian will be kind enough to implement it.

For Cloud users, I can confirm that setting a "none" or "unspecified" default priority + a validator "Field Priority should be modified during the transition." does NOT work.

@Atlassian it would be nice to understand what are your plans on this. Last official answer if 4 years old and there's a significant number of requests/inputs here.

I'll admit again, though, all of these are work-arounds though.

@joel
I think I mentioned this in a sooner post, but we just created a default priority of "no priority selected".  There is a couple of options on what to do from there.  In our case, we have a some custom integrations to do the following:

• Jira tickets can be entered from confluence pages (especially used for our internally reported incidents which need a suggested priority).  Our integration from the marketplace allows us to set what options are available from the full set of options.  We mark this field as required, but ommit the submitter from being able to select "no priority selected".
• (push system) We use automation for Jira for many things, but one thing you can also do is send slack messages on certain events and conditions.  If needed you could set someone or a channel to get pinged when someone submits a ticket with the priority set to the default "no priority selected (with more constraints if desired).  This allows someone to be notified to follow up

• (pull system) Further more, we have a audit dashboard that looks for inconsistent states in Jira and call them out to be fixed via jql filters.  you could make a JQL filter that is present on one such dashboard (that someone could setup as their Jira homepage everytime they log in) to show tickets with "no priority selected" as set on a ticket.  This, again, allows the visibility for someone to follow up and get a priority assigned.

+1 This is still needed.

Yup. Ours is named "Unspecified" and has a transparent white little icon.

Matt Song - For the last couple of years, we've solved this by defining a priority called 'Not Prioritized' and setting that as the default (there's even an icon that's a circle with a dash in it that seems appropriate).

It works well enough to indicate when a ticket has not been explicitly prioritized.

+1 This is still needed. Anyone find a solution?

Same need.

I really don't understand how this can be so hard to implement. This is a common request on most of systems I've been using and developing and make so much sense.

+Vote!

12 years Gathering interest nice!

This would help our team from erroneously labeling new submissions

This would be very helpful for our team as well!

We need it badly! +1 for priority field being empty and mandatory for users to make a choice. 

l would like this feature to enable us to make this field required but force the user to make a decision.  With a default value the user doesn't have to choose and can save with the default value in the select list rather than actually selecting something. 

I would very much like this functionality to force user to set priority for each issue instead of using default priority

+1 for priority field being empty and mandatory for users to make a choice

I like this idea, and I like the corresponding bug reported in relation to Issue Type (JRASERVER-30620). They would allow administrators to force users to make decisions based on the information available to improve the quality and usefulness of the data in the issue logged.

This is even more misleading now that priority schemes are released...if you don't identify a default in your scheme, one would assume that means you want it to be empty, not that you don't mind if Jira picks a default for you.

Admittedly I'm just trying to make lemons into lemonade and would like the real solution too.  As stated above though, this will at least not give a real priority that is also the default (our was "low") to every ticket, which confuses everyone down stream about "which ones are really low, and which ones were just the default value that I need to talk to the reporter about a real priority".  That at least have a flag now for ones where the reporter did not set the priority value and can reach out about their thoughts on priority.  Not optimal, but at least gives us a chance of not having someone mark something as the default (which was low) and coming to us a week later saying it's the most important thing in the world and interrupting our sprint.

I am not in favour of the proposed workaround either. The ideal solution would be a mandatory Priority field that opens without value, and which requires users to make a deliberate choice...

We need the priority which it will be "None" and then user create issue it must choice priority (mandatory)

thanks for input. We will also go for a a "not set" default value. Our policy is that - not set - state is not allowed and thus we would like to tool enforce that. But in this case of possible invalid state over possible invalid value - ill take invalid state = default not set value

il look at the transitions thing also

Pffffft. I added an Unassigned value and set it as default. Tried to put a 'value must change' condition on the Create transition to New....it doesn't respect it. I guess it considers setting the default a change.

Although it may not solve all cases, we've added a default priority of "unassigned" or "not set" so at least the prioritizor of this ticket knows the requester didn't put in a priority when putting in the ticket.

im a bit surprised that a ticket system like Jira does not support this. Getting trustworthy prio on tickets is key.

@Sarathi - It seems that you actually have a Priority called "Not Prioritised" defined as the default value. In your case you only need to remove this defined value and need to set the priority to one of the remaining values.

Created:09/Jul/2007 1:35 PM - 10 years !! really ??? 

Simply put - how do I ensure someone puts one of the 3 Priority levels we have ?

The * appears but one can leave it as Not Prioritised ! ? 

Is there anymore progress on this?

I can make every other field with 'None' as a value a mandatory requirement for the user to complete on initial defect creation apart from 'Priority' which is an important field.  Although it adds the "required" asterisk it just doesn't do the "required" activity.

Do we have a solution for this ?

Setting Default Issue Type to "None" Ignored

We need this also, not sure why dose it have to have a default value.

Dear Team, 

could you set this suggestion? 

It will be cool, then we are setting js or workaround by transition.

Thank you. 

This looks like a bug as mentioned from previous comments. You can set the Priority field as required on field configurations and validator but can't set it to blank on purpose?

I also tried this workaround with no luck on the server installed version of the product. Would love to be able to remove the default. It causes people to leave it on the default (medium) instead of setting it to an appropriate level. Unfortunately without this feature working it means people put things in with invalid priority.

Hope this gets fixed soon.

Hmm, maybe it's a cloud thing

matt, thanks for chiming in! What I'm saying is that I did what you described and it doesn't have the effect you described.

In the config area, the Priorities screen, none of the priorities was marked as default. But when I create a new ticket, the priority dropdown is defaulting to P3 (which was not the most recently selected default).

FWIW, we're using the cloud instance, not hosted.

I guess your instance has chosen a default for the Priority. If you can't unselect the default you can try (in staging first): create a new Priority opion, make it default, delete the new Priority option. Now no option is default