Severity Fields in a Project don't Sort Correctly

[Manoj Dasari]

We have n number of issues in a project and we are using JQL to get the issues in order but 

we are getting like 

Ticket number  Severity

Ep-01                 s2

Ep-02                 S1

Ep-03                  s3 like this

[Trudy Claspill · Accepted solution]

Hello @Manoj Dasari 

What type of field is the Severity field?

[Manoj Dasari]

Its a Select list (Single choice)

[Trudy Claspill]

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.

[Trudy Claspill]

Hello @Manoj Dasari 

You previously marked my Answer as Accepted. Has something changed? 

Is "getting three severity fields" something new that just started occurring?

Can you provide a screen image?

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

What is the "order by" clause in your JQL?

[Manoj Dasari]

while using the JQL we are getting the three severity fields.