We are using a customized priority scheme for one of our server project and the priorities are,
(We have sorted priories as per above order in the scheme)
But when we are sorting the issues in the filter based on priorities, the issues are sorted differently, always medium is coming in the top even though we are not using any default priority.
Please help us to resolve this issue.
Unfortunately it's a limitation in Jira.
The Priority scheme just displays your custom order in the Priority dropdown list.
When using in JQL though e.g.
ORDER BY priority DESC the priority is ordered using your default Global Priority scheme (Admin > Issues > Priority schemes).
Here's an excerpt from Jira's documentation
It's important to know how JQL works with priorities. If you use JQL to order issues by their priorities (e.g. descending), they will be ordered according to the importance of the priorities on the global list of priorities. The global list is what's displayed on the Priorities page. The order from priority schemes is not relevant for JQL. To put it in an example, let's say the priorities in your Jira instance are arranged in the following way:
Global list (Priorities page)
Custom priority scheme
After appending a JQL query with e.g.
ORDER BY priority DESC, the Urgent issues will be at the top of the list (followed by Highest, and then Medium), even if they’re in a project that uses the custom scheme. You can change the order in the default scheme on the Priorities page.