-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
148
-
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
-
JRASERVER-23302 Priority field in sub-task quick create form does not respect global default
- Closed
-
JRACLOUD-13048 Allow 'No default' for Priority
- Reviewing
-
JDEV-38063 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...