Limit the number of global Priority options per project

[thomas.drake]

Hi,

Our global priority list currently has the following options:

P1-P4

High-Low

Blocking, Critical, Normal, Small

This list is in use across all of our projects, from software to service desk. We use this list for service desk as this is the field that triggers alerts in opsgenie. However, our clients are starting to complain about the non-P1-P4 options being selectable when they enter a ticket into our support portal. 

The non-P1-P4 options are currently used by the software teams. 

My question is - can we limit the number of options available on customer's ticket portal without deleting them from this list? Or will I need to create a custom priority field for the software team to use and then recreate the options they're currently using there instead?

Thanks,

Tom

[Trudy Claspill]

Hello @thomas.drake 

There is a change request to enable the Priority Schemes feature that is currently available on in Jira Server/Data Center, which would allow you to create Priorities per project.

https://jira.atlassian.com/browse/JRACLOUD-3821

[srikanth u]

Hi @thomas.drake 

Couple of years ago, we have the same problem and we have mitigated by incorporating a new field called "Client Service Priority" and for the development team we used the Jira provided "Priority" field, that way we can ensure that both the priorities preserved.

Thanks!

Srikanth.