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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
We currently have a list of 11 default values for the priority field (shown below and not in that order)
I have run a quick search and they're all currently being used, but I would like to tidy up this list given they are a few duplicates/ones that mean the same thing.
If I was to delete one already being used, would it give me the option to associate this to another one (as it does when you change workflows etc). Is there a better way to do it?
Thanks
Hi @Matthew Hine ,
Don't worry. When you delete a priority, Jira will show a screen to choose another priority for issues matching deleted priority.
Hope this helps!
@Thuan, Do Dang Thanks for the information, thats what i was hoping it would do. I just need to understand how what reporting if any is done off the back of the priorities and make sure all users know these will be changing
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Matthew Hine ,
This change will affect all filters/reports use direct deleted priority value.
To make sure all users know these will be changing, I think you should announce users about the changes, the time you apply the changes, and maybe a guideline about using new priorities.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks again. I will try out using the banner option to see if this works (never used it before) as think this will be an easier way to notify everyone in advance of any changes being made
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Matthew Hine ,
my suggestion is to create a specific Priority Schemes for your project and associate to your projects.
Next, associate your priority scheme with a project.
This should fix your issue.
Hope this helps,
Fabio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the reply. I didn't think priority schemes were available for the cloud version? I cant see this option within the admin options.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Priority Schemes are not available in Jira Cloud.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.