query result sorted on Story Points displays unexpected order
There are many recent posts and questions regarding the query result page sorting function.
eg.
2 answers
Also, if you've been bitten by added entries to complexity you'll recall that their ID are numeric strings. Even when sorting those they don't order correctly (unless converted to integer values).
<enumeration attributeTypeId="complexity" name="complexity">
<literal default="true" id="0" name="0 pts"/>
<literal id="1" name="1 pt"/>
<literal id="2" name="2 pts"/>
<literal id="3" name="3 pts"/>
<literal id="5" name="5 pts"/>
<literal id="8" name="8 pts"/>
<literal id="13" name="13 pts"/>
<literal id="20" name="20 pts"/>
<literal id="40" name="40 pts"/>
<literal id="100" name="100 pts"/>
</enumeration>
sort alphabetically is:
0
1
100
13
2
20
3
40
5
8
<enumeration attributeTypeId="complexity" name="complexity">
<literal default="true" id="0" name="0 pts"/>
<literal id="1" name="1 pt"/>
<literal id="2" name="2 pts"/>
<literal id="3" name="3 pts"/>
<literal id="5" name="5 pts"/>
<literal id="8" name="8 pts"/>
<literal id="13" name="13 pts"/>
<literal id="20" name="20 pts"/>
<literal id="40" name="40 pts"/>
<literal id="100" name="100 pts"/>
</enumeration>
sort alphabetically is:
0
1
100
13
2
20
3
40
5
8
This kind of issue is caused by sorting feature is sorting by id instead of name.
A known enhancement has been opened: sort of enumeration should based on name rather than id (175676)
