How do I disable the Priority (Priorities) field from displaying in a Request Type?
Asked by Andy:

Hi everyone,

There seems to be a global field that Jira uses across many different types of products called Priorities. In the implementation I'm using, this field has been mis-managed and is absolutely huge. I can't change d the Priorities list as it will affect multiple projects so I don't want to use or see that list, period. Instead, I've created my own 'Priority' field that contains just what I need.

The problem is, that the Priorities based Priority field (let's call it PP) appears as a default in every Request Type. I have checked the field configuration but cannot find the PP field to remove it from the field layout, and the only solution I can find is to hide the PP field from every Request Type and it doesn't feel like a good solution.

I'm assuming I'm missing something. Can you please enlighten me oh wise ones.

Thanks


Answers:
author: Curt Holley
body: I hate to say this [@Andy](https://community.atlassian.com/t5/user/viewprofilepage/user-id/4722468) but ultimately the best solution is to tackle the actual problem and consolidate the out of control list of priorities configured in the PP field (as you call it).

Yes, this will mean getting everyone on the same page and agreeing of which ones to keep and drawing up a mapping of existing (to be retired) priorities and which one to migrate them to as part of this tidy up exercise.

Why create another field for the same purpose....it will not behave like the system one, it will just be a custom field....plus, this will only complicate the overall configuration more and not fix the problem with the actual priority field.

comments: author: Curt Holley
body: As suggested [@Andy](/t5/user/viewprofilepage/user-id/4722468) . Thanks!!!


author: Andy
body: Thanks both for your suggestions but I don't think either of them work. The problem is that while I can remove the system Priority field from the Issue Types screen, it doesn't remove it from the Request Type unless I hide it. I also can't hide the field in the field configuration because that would affect many projects, not just mine.

Is there another way?

comments: author: Curt Holley
body: I hate to say this [@Andy](/t5/user/viewprofilepage/user-id/4722468) but ultimately the best solution is to tackle the actual problem and consolidate the out of control list of priorities configured in the PP field (as you call it).

Yes, this will mean getting everyone on the same page and agreeing of which ones to keep and drawing up a mapping of existing (to be retired) priorities and which one to migrate them to as part of this tidy up exercise.

Why create another field for the same purpose....it will not behave like the system one, it will just be a custom field....plus, this will only complicate the overall configuration more and not fix the problem with the actual priority field.


author: Andy
body: I agree Curt, it's the right thing to do. I won't be able to make that change for various reasons but if I could, I would. Thanks for taking the time to give your advice.


author: Andy
body: If you'd like to copy/paste your suggestion into as an answer, [@Curt Holley](/t5/user/viewprofilepage/user-id/3527535) I can accept :)


author: Fabian Lim
body: Hi [@Andy](/t5/user/viewprofilepage/user-id/4722468)

I believe you could also update the field configuration to hide the priority field. Here is a quick video tutorial: <https://youtu.be/C3Lb1T4liGw>


author: Ravi Sagar _Sparxsys_
body: Hi [@Andy](/t5/user/viewprofilepage/user-id/4722468)

Yes, you need to remove it from the Request Type's and/or also from the mapped issue type.

Ravi


Tags: field

priority

screen