Query on enumerated fields returns incorrect results
Description: When running a query that looks for a custom field value, usually enumerated, the results it returns are not accurate. For example, if the field has values of 1, 2, 3, 6, 4, 5 in that order, a query that looks for same or greater than 1 AND less than 6 will not return the 4 and 5 results. It will stop at 6 and only return the 1, 2, and 3.
This goes for alpha values in the custom field. If the values are alpha, beta, zeta, gamma, delta, the a query of same or greater than alpha AND less than zeta will only return alpha and beta.
Answer/Solution: When an enumerated custom field is created for a CR, and several values are entered, if they are named out of order, then the query does not work correctly. If the name values are in numeric or alpha order, then the query works fine. This is a bug with StarTeam 2006 R2 (through build 22.214.171.124). what is happening is that the name values are being resolved out to the code value and the query is run on that order. So it returns all the results that are less than the name value as it relates to the code value.
For example, the code value for alpha is 101, for beta it is 102, zeta is 103, and delta is 104. If the query is run and told to look at anything less than zeta, it is actually looking at anything less than code 103.
If you are experiencing this issue, please contact support. A
defect CR has been entered for this issue and it should be resolved
in a future build.