Is it ok to change Priority Names?

[Manjula Varadharajan]

Currently we have Priority Names as Critical, Blocker etc.  Is it OK to change to P1-Critical, P2-Blocker etc? Would this impact users' saved filters and reports that use the Priority field? What other impact may this have?

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

The change will be made globally (across all projects). And will impact filters (and hence reports/gadgets etc using them) using the priority names. Can't think of anything else now.

[Sujit Pathak]

You can update the label of the issue Priority through the navigation

Project > Setting > Issues > scroll down  to "Priorities" > View Priorities > Edit and Update

:/secure/admin/ViewPriorities.jspa

[Sten Sundelin]

You can, but I would strongly advise against it except on a brand new system. Many users will use the priority names in filters (and more) and if you change the names, they will probably break.

[Nic Brough -Adaptavist-]

Some saved filters may be affected, it depends on how they have been created and stored.  If there are filters that stop working because of a change, your users will see an error message and the owners can easily go correct them.

The name of the priorities is a label rather than an absolute in most places.  JIRA works in the background with priorities named 1, 2, 3, 10010, 10020, etc, but displays Critical, Blocker, Medium, Flibble - whatever labels you choose.  So most places will not be directly affected by a simple name change.  (The analogy I've seen is that "repainting your house a different colour does not change its street number or post-code"!)