-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
89
-
22
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; unfortunately we don't have any plans to support this in JIRA for the foreseeable future.
Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
Original request description
I would like an option where the Priority is set to 'empty' by default and then the user has to select one of the options in the drop down list (this should be mandatory).
This functionality already exists when adding a custom field.
It is quite important that the priority should be undefined and that the user has to pick one of the options. Otherwise people might overlook the priority and just leave it automatically on the default value.
- is related to
-
JRASERVER-30620 Setting Default Issue Type to "None" Ignored
-
- Closed
-
- relates to
-
-
- Closed
-
-
- Reviewing
-
JDEV-38063 Failed to load
- mentioned in
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
[JRASERVER-13048] Allow 'No default' for Priority
How do you block a priority value from being selected, thus forcing the user to pick another one?
How is this not solved yet!?
Because there's literally no incentive for them to do so; they know everyone will keep using Jira regardless.
Although, that of course could change.
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.
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.