Query is not sorting as expected!..
I have created a query of the work items in the current sprints. The query is very simple, ID and Summary, sorted by Summary in ascending orders.
The results are: Cons... Cons... Proto... Proto... Valid... then starts over at Cons... Const... ...etc. What is even more annoying is that when I add the filter to the query to select only where Summary starts with "Const", I get the list of work items in the top group only and none in the lower group. I have copied the exact text for the first few letters from a work item in the top group into a work item in the lower group thinking may be hidden characters but still received the same results. Anybody hit a similar snag? Thanks. Ammar. |
5 answers
I have created a query of the work items in the current sprints. The Are you using Oracle? There is an issue with medium sized string fields (like Summary). It is documented in http://www-01.ibm.com/support/docview.wss?rs=3488&uid=swg21410689 -- Regards, Patrick Jazz Work Item Team |
Yes... we are using Oracle, what are the options? I will read more on the issue.
|
http://www-01.ibm.com/support/docview.wss?rs=3488&uid=swg21410689
is not valid link. |
http://www-01.ibm.com/support/docview.wss?rs=3488&uid=swg21410689 There is currently a replication problem with the technote and it is temporarily unavailable. I am copying its contents here: === Problem(Abstract) IBM Rational Team Concert work item queries for tags can return a result set that does not contain all work items that have the tag. The missing work items are the ones whose tags field was updated after creation. Symptom Using the Tag Cloud View, you can see for example, 10 matching work items for a tag. When you click on the tag, the Work Items View shows fewer results. Creating a query for tag X does not return all matching work items. Cause Oracle does not make a distinction between 'null' and the empty string. In order to emulate the distinction, string fields on Oracle get a specific prefix. Queries for this field automatically include the prefix. When a medium sized string field like 'Tags' is updated, the prefix is mistakenly not added, which leads to this issue: The query includes the prefix, but the field does not have it --> No match. Refer to jazz.net work item 96557 for full details. Environment Microsoft Windows and Linux. Affects only Oracle based installations. Diagnosing the problem Incomplete query results for tag based queries Repository database is Oracle Resolving the problem In order to fix the problem for existing work items, you need to run repotools -cmd=fixOracleStrings For more information about the command, please run repotools -help cmd=fixOracleStrings includeHidden == -- Regards, Patrick Jazz Work Item Team |
http://www-01.ibm.com/support/docview.wss?rs=3488&uid=swg21410689 http://www-01.ibm.com/support/docview.wss?rs=3488&uid=swg21410689 is back online -- Regards, Patrick Jazz Work Item Team |
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.