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
We recently found that the priority in the jira project was abnormal, before the default was "Medium", now the default is "Blocker", most of the projects in our project use the system default priority scheme, to confirm what the problem is, we want to create the issue, the default is "Medium".
A few things that you should check -
1) In the server env, one can create custom priority scheme at each project level (i.e. with different options defined in the Default Priority Scheme + different default priority value).
2) You should check the priority scheme applied/associated with your project(s) in question to see which scheme is using. Then you need to access the scheme's configuration to determine what is the default option is setup to.
3) If you have multiple system admins, then you need to ensure that all the admins understand that any changes against configurations (i.e. schema, WF) and if they are shared by multiple projects, then the changes will impact all the projects.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team
In the current project, the default priority scheme is used, I understand what you mean, you can create a new priority scheme for specific projects to configure, but this is not the effect I want
What I need to change is the priority option of the default priority scheme. I found that the default priority is "Low" in my test environment and "Blocker" in the production environment. I wonder if I can change the default option of the default priority scheme in the server background or in the database
You just need to access the default priority scheme in your specific env from the Jira Administration icon (located in the upper right of the screen) and go to "Issues".
Once you are in the "Issues" UI, then go to "Priority schemes" option and edit the scheme in question to change the default option as needed.
This can be done via the Jira UI. Never try to conduct update directly via the backend database. I am assuming that you are a member of the system admins for your env. If you are not, then please reach out to your system admins team and work with them to update the default priority scheme.
Lastly, since it is the default priority scheme, all changes to the scheme will impact to all the projects that use the scheme.
Hope this helps. If so, please click on "Accept answer" so others with similar asks will see this post as an answered one with solution.
Very odd. I would recommend you to create another scheme (copy it same as the default priority scheme setup), then adjust the default priority option and apply the new scheme to all of your projects as appropriate.
In our env, we can see the Edit option. I just came across this enhancement request in Atlassian - https://jira.atlassian.com/browse/JRASERVER-66660. There is an workaround mentioned in the request, I don't know if it is applicable to your env. Take a look and determine.
By the way, what version of Jira/JSM you are running on right now?