I imported hundreds of issues from CSV to build my project.

I don't have a priority field in my issue configuration, so none of my imported issues have priorities and none of them show any icons when viewing a task and its sub-tasks. All of their priorities are set to "None."

However, when you create a new issue from inside Jira, suddenly it gets a priority. It now has an icon when viewing a list of sub-tasks (but not an icon when viewing the individual task since priority is not a field).

As usual I can paste an image into this box but then you delete it, because why would you want visual confirmation of your endless stream of bugs?

The first two sub-tasks were created by Import; the last by Create while in Jira.

Perhaps the very first question is WHY DOES IMPORT CREATE IMPOSSIBLE ISSUE SETTINGS?

The second question is, since Jira obviously supports not having a priority, why can't I give an issue no priority?

The third question is, do you people test this software at all? I mean, even once? Does any of your staff ever actually use any of the features of Jira and see if they interact the way you expect them to?

Every single day I use Jira I find some bug like this, where it is clear no one ever spent even two seconds thinking about completeness or system interaction.

Hi 5709a757b17f thanks for your feedback - this ticket was reopened 3 days ago. I added notes about the limitations of the workaround I shared to the ticket's Description.

@Anusha Rutnam I do not believe you have resolved the issue as requested. In managed field configuration environments this solution removes it for all projects. Additionally, the indication that it should be aligned to specific issue-types is also assumptive in managed environments where that decision can be agreed upon. 

Perhaps I am misunderstanding your suggestions completely, but changing the field configuration requires requests to our internal team which will be unlikely to be adopted.

The original request states that the priority field be turned off from display at the backlog and board levels, please reopen and add a control to project or board settings. It can be done with a simple checkbox and require no administrative configuration for individual projects inside managed environments

Update: This ticket has been reopened. The field config option is not suitable for all use cases.

e36220c5a1ed no, field configurations do not need to be project-wide. You can have a different field config for each issue type: Associate field behavior with an issue type

Wouldn't hiding the priority in field configuration also hide it for all issue types in the project?

In our situation we want to hide them from stories and other related issue types, but not from production defects.

Update: This ticket has been reopened. The field config option is not suitable for all use cases.

Please correct me if I have misunderstood but I believe this is already possible by hiding the Priority field in your field configuration as described in this Community post.

The following screenshots from my company-managed Jira Software project that uses a Kanban board.

Board before hiding Priority:

Board after hiding Priority:

 
Backlog before hiding Priority:

 
Backlog after hiding Priority:

This would be a great quality of life improvement. Please prioritize.

This would be a great quality of life improvement. Please prioritize.

In our small team we prioritize by stacking issues on top, so we do not really need priority field and would like to be able to make it disappear from the boards. Thanks in advance. Cheers, Stefano