You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
For one specific team-managed project, I want to adapt the values of the priority field without interfering with all the other existing projects.
Hi @Marc Schijvaerts , welcome to the Atlassian Community and thanks for your question!
It should be possible for you to set up a custom priority field for a team-managed project. Team-managed projects do not share their configuration so whatever changes you make to the configuration does not impact any other project, team or company managed.
Did you mean that you want a different set of priorities for a company-managed project?
How do you change the priorities though? I am not a Jira Admin, only a Project Admin. And we have a Team-Managed Project. You only get this from the Project Settings:
You can only change the Default value, but not the actual names of the priorities (Blocker Critical, Major, Minor, Trivial).
How can you change the name of the priorites?
It will not be possible to modify the values in the Jira system Priority field.
However, you can create your own Priority custom field and use those values in your project.
From the project settings, select the Issue Type you want to add the field to
Then, on the right, create a new custom field and call it Priority. Then, you can come up with your own priorities instead, which are specific to this project.
I hope this helps.
Hi Valerie, thanks for the support. I knew of that workaround already but then we'd lose the icons which are particularly useful to quickly identify tickets and also for Dashboards and Boards.
Jira Cloud does not support "priority schemes" like Server/DC does, so there's no way to have different priorities per project. Your only way to do this is to define a simple select list local custom field to a project (which will not have any of the functionality of priority, like icons)
It is on the way, but I do not know if it will apply to Team-managed projects.