When an issue is set to Priority 'Non Significant' (lowest priority), it is not possible to change to another priority. The Priority-dropdown (that usually lists all priorities) says 'No matches found'.
When using bulk change functionality I can perform the change of priority, but not from the issue view. (See screenshot of Priority dropdown).
Any idea if this is a configuration gone wrong or a bug i JIRA?
I do not think we have done any adjustment to the priority field that differs from the default configuration, but I can be wrong...
OK thank you @Yogesh Mude
My conclusion from those related discussion is that:
1. If I was on Server (not Cloud) JIRA I could solve this by configuration in Priority Scheme. => Not a possible solution for me since I am on Cloud.
2. Go back to the old Issue View in Settings.
=> I will try this and see if that helps. Not fun to go back though, when I got used to the new Issue View.
Could I report this as a bug to Atlassian?
How does this community work, could you give my any tip on that?
I think this has been reported to Atlassian already and if you want you can report to https://support.atlassian.com or if you find any similar ticket then you can vote on that.
As per my understanding, the issue occurred whenever you will use the default priority scheme, so try to copy and create a new priority scheme and associate to respective project then check.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But again, priority scheme do not exist in Cloud solution, so I cannot use that workaround.
I tried changing back to the old 'Issue View' using my personal settings (under Jira Labs section).
This solves the problem.
Thank you for you inputs, I will report this problem concerning the new ISsue View to Atlassian to be sure.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the Atlassian community.
There are lot of discussions happened on the same issues previously on the community, to sort out the same please have a look at the below.
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.