RTC Query Sorting not working well in Web Client
Hello,
In our use of RTC 2.0.0.2, we have User Story queries with multiple fields in sorting criteria. What we found is in Eclipse client, such sorting works fine, but in Web client, RTC seems to always use the first field in the sorting criteria list, and ignore all other fields in the list.
This issue has caused the order of the user stories in the query result to always change. Given most of our team members rely on the Web client in scrums, the user story owners can't speak in the order that people expect in the daily scrum meetings, which has caused many confusions.
Are there any solutions to this issue?
Thanks.
P.S. the fields used in the sorting criteria are standard fields such as "Filed Against" and "Status" -- not custom attributes.
In our use of RTC 2.0.0.2, we have User Story queries with multiple fields in sorting criteria. What we found is in Eclipse client, such sorting works fine, but in Web client, RTC seems to always use the first field in the sorting criteria list, and ignore all other fields in the list.
This issue has caused the order of the user stories in the query result to always change. Given most of our team members rely on the Web client in scrums, the user story owners can't speak in the order that people expect in the daily scrum meetings, which has caused many confusions.
Are there any solutions to this issue?
Thanks.
P.S. the fields used in the sorting criteria are standard fields such as "Filed Against" and "Status" -- not custom attributes.