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
Hello, I need to set up a new set of priorities limited to one project, but in Settings>issues> Priorities, I am not able to see the priority schemes.
Are there any limitations to the standard plan we currently at, or this feature is not available anymore.
Hi @Janka Lengalova , thanks for your question.
Priority schemes don't exist in Jira cloud, there is just one central list, as opposed to in server.
Hi @Janka Lengalova , there is a suggestion for priorities by project here, [JRACLOUD-3821] Priorities per Project - Create and track feature requests for Atlassian products., so you can follow that.
Otherwise, you could create, for example, a team-managed project, where you could have priorities that are different from the system ones, but I don't know that I would recommend that as an approach, especially as you asked about a JSM project.
What is the desired behaviour / outcome you are seeking?
A possible workaround could be to create a custom field or a series of custom fields and then use an automation to derive the priority. You might have two custom fields of like urgency and scale of the problem, let's say, and if those are both high, you could have an automation that sets the priority of high, if you want to avoid that requestors choose the priority.
Is that what you are trying to achieve, or is it something else?