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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have multiple priority levels that we use specific to bugs (Highest, High, Medium, Low, Lowest). I just added Must, Should, Could, Won't to our drop down choices for priority.
For BUGS: I only want to have the choices in the drop down for Highest, High, Medium, Low, Lowest
For all other issue types (Epic, Story, Task...) they can see all choices or I can limit those too -- its less of a big deal for these issue types.
I just don't want users getting confused when working with bugs and not knowing what priority to choose since this is a new feature we are implementing.
Anyone know how to do this?
Hello @Jennifer Baum
There is no feature natively available for limiting the values in the built-in Priority field based on the issue type.
You could create your own custom field for Priority, and then create Contexts that set different values per issue type and project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.