Earn badges and make progress
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
Next: Root
1 badge earned
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
Rise up in the ranks
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Come for the products,
stay for the community
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
2 answers
1 accepted
If Severity is the one and only field declared in your ORDER BY clause, it appears that the issues will be sorted based on the order of the options in the Context definition, with DESC being from the bottom of the list options to the top, and ASC being from the top of the list options to the bottom.
The ORDER BY clause will not cause the results to be sorted based on an alphabetic sorting of the list option values.
Compare the images below.
The first one shows the Context definition order of the list options along side an issue search that is ordering the issues by that field.
In the second image I have change the order of the options in the Context definition and re-executed the search. The order of the search results has changed to match the order of the the options in the Context definition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.