Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Unable to sort by priority on Web UI

Apologies if this has already been posted in a forum or in a work item - I did a thorough search of both and could not find anything directly referencing the problem I'm seeing.

When I run a basic work item query using the Web UI, if I click on the "Priority" column it does some sort of sorting, but not in any apparent order I can see - for example, I get all the 8's and 7's at the top, then the 3, 4, and 5's, then the 1 and 2's, then the 6's, and then the 9 and 10's. Clicking again just reverses these same groupings.

Same thing happens if I try to add a sort criteria to the query itself.

The Eclipse client sorts them correctly.

I did see a defect from 1.0.0.1 which described a similar problem where things were being sorted by the priority "name" (High, Medium, Low) and not the number, but that does not seem to be the case here since those 3 things are not being grouped together at all.

0 votes


Accepted answer

Permanent link
Apologies if this has already been posted in a forum or in a work item
- I did a thorough search of both and could not find anything directly
referencing the problem I'm seeing.

When I run a basic work item query using the Web UI, if I click on the
"Priority" column it does some sort of sorting, but not in
any apparent order I can see - for example, I get all the 8's and 7's
at the top, then the 3, 4, and 5's, then the 1 and 2's, then the 6's,
and then the 9 and 10's. Clicking again just reverses these same
groupings.

Same thing happens if I try to add a sort criteria to the query
itself.

The Eclipse client sorts them correctly.

I did see a defect from 1.0.0.1 which described a similar problem
where things were being sorted by the priority "name"
(High, Medium, Low) and not the number, but that does not seem to be
the case here since those 3 things are not being grouped together at
all.

The query results are sorted on the database. The value stored for the
Priority in the database is the ID of the Priority literal, e.g.
"priority.literal.l1". If you customize the Priority enumeration, make
sure that the IDs are in the desired order (check the process XML), e.g.:

1 : priority.literal.01
2 : priority.literal.02
3 : priority.literal.03
4 : priority.literal.04
5 : priority.literal.05
6 : priority.literal.06
7 : priority.literal.07
8 : priority.literal.08
9 : priority.literal.09
10: priority.literal.10

--
Regards,
Patrick
Jazz Work Item Team
Millard Ellingsworth selected this answer as the correct answer

0 votes


2 other answers

Permanent link
Apologies if this has already been posted in a forum or in a work item
- I did a thorough search of both and could not find anything directly
referencing the problem I'm seeing.

When I run a basic work item query using the Web UI, if I click on the
"Priority" column it does some sort of sorting, but not in
any apparent order I can see - for example, I get all the 8's and 7's
at the top, then the 3, 4, and 5's, then the 1 and 2's, then the 6's,
and then the 9 and 10's. Clicking again just reverses these same
groupings.

Same thing happens if I try to add a sort criteria to the query
itself.

The Eclipse client sorts them correctly.

I did see a defect from 1.0.0.1 which described a similar problem
where things were being sorted by the priority "name"
(High, Medium, Low) and not the number, but that does not seem to be
the case here since those 3 things are not being grouped together at
all.

The query results are sorted on the database. The value stored for the
Priority in the database is the ID of the Priority literal, e.g.
"priority.literal.l1". If you customize the Priority enumeration, make
sure that the IDs are in the desired order (check the process XML), e.g.:

1 : priority.literal.01
2 : priority.literal.02
3 : priority.literal.03
4 : priority.literal.04
5 : priority.literal.05
6 : priority.literal.06
7 : priority.literal.07
8 : priority.literal.08
9 : priority.literal.09
10: priority.literal.10

--
Regards,
Patrick
Jazz Work Item Team

Thank you very much for the quick reply - I contacted our process administrator and I guess they had indeed made some modifications to the priority field template and when we looked at the xml file the id names they had were not named in a way they would sort correctly. Once we fixed these (fortunately we are both handy with doing mass updates) the sort order works correctly.

I don't know how to mark this as "resolved" but my problem is fixed. Thanks.

0 votes


Permanent link
I don't know how to mark this as "resolved" but my problem
is fixed. Thanks.

Thanks for the feedback. Marking something as "resolved" is only needed
for work items. Posts in the newsgroups are less formal.

--
Regards,
Patrick
Jazz Work Item Team

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Feb 23 '10, 11:11 a.m.

Question was seen: 5,447 times

Last updated: Feb 23 '10, 11:11 a.m.

Confirmation Cancel Confirm