Severity not sorting correctly in Web Client query output

When we use the Severity field in Queries the Sort isn't working in
the correct order.

I had deleted the default enumeration values that came "out of
the box" and replaced with what's below to match our current
system.

When I click the column in the query output to sort the order goes 4,
1, 2 ,3 when we want to see 1, 2, 3, 4 in ascending value.


This only affects the Web Client...Eclipse sorts in the 1,2,3,4
order.

Is this a defect?

Ordering in the Web UI is done on the repository using 'order by'. When
you create your own literals, make sure that their IDs are chosen such
that they sort alphabetically in the desired order.

The Eclipse UI also uses the repository's 'order by' when the query is
executed, but when you click on the column header, the result is ordered
on the client, which may be different from what the DB does.

--
Regards,
Patrick
Jazz Work Item Team

Thanks Patrick,


My Severity enumeration is defined as below. Is it possible its not seeing the "0" at the end of "severity.literal.l10", which is why it sees that entry as the top entry instead of "severity.literal.l7"?



<enumeration attributeTypeId="severity">
<literal icon="processattachment:/enumeration/critical.gif" id="severity.literal.l7" name="1"/>
<literal icon="processattachment:/enumeration/high.gif" id="severity.literal.l8" name="2"/>
<literal icon="processattachment:/enumeration/medium.gif" id="severity.literal.l9" name="3"/>
<literal icon="processattachment:/enumeration/low.gif" id="severity.literal.l10" name="4"/>
</enumeration>

Removing the Enumeration entry in the Properties of the Severity field seemed to fix this on the Eclipse client, but the Web Client is still sorting as 4,1,2,3.

My Severity enumeration is defined as below. Is it possible its not
seeing the "0" at the end of
"severity.literal.l10", which is why it seems that entry as
the top entry instead of "severity.literal.l7"?

Unfortunately, your XML was eaten by the forum software.

But in general, only collator-based sorting would order these literals
as expected:

severity.literal.l7
severity.literal.l10

You would need to specify them as

severity.literal.l07
severity.literal.l10

Then the sorting should work in the Web UI, too.

--
Regards,
Patrick
Jazz Work Item Team

My Severity enumeration is defined as below. Is it possible its not
seeing the "0" at the end of
"severity.literal.l10", which is why it seems that entry as
the top entry instead of "severity.literal.l7"?

Unfortunately, your XML was eaten by the forum software.

But in general, only collator-based sorting would order these literals
as expected:

severity.literal.l7
severity.literal.l10

You would need to specify them as

severity.literal.l07
severity.literal.l10

Then the sorting should work in the Web UI, too.

--
Regards,
Patrick
Jazz Work Item Team


That fixed it...thanks Patrick.

I am seeing similar issue as well with sorting in the web. Are you suggesting to make these changes directly in xml source file on the process configuration tab? Are there any repercussions with DW or will it automatically sync previous values without any issues?

Below is the information on our literal values.

<enumeration attributeTypeId="severity" name="severity">

<literal default="true" icon="processattachment:/enumeration/unassigned2.gif" id="severity.literal.l8" name="Unassigned"/>

<literal icon="processattachment:/enumeration/critical.gif" id="severity.literal.l5" name="1-Critical"/>

<literal icon="processattachment:/enumeration/major.gif" id="severity.literal.l4" name="2-Major"/>

<literal icon="processattachment:/enumeration/medium.gif" id="severity.literal.l7" name="3-Average"/>

<literal icon="processattachment:/enumeration/minor.gif" id="severity.literal.l2" name="4-Minor"/>

</enumeration>


Thanks
Samir