When I create a query and sort the results based on a custom enumeration in a custom attribute, it appears that the results are sorted on the literal value rather than the named value.  My PMR was closed stating this is functioning as designed, but would like further input to understand if this should be a Defect or Enhancement Request.  Below is an example scenario:

RTC Project Area (created per application) includes an attribute called PMO Project.  This attribute contains the following enumerations that were create when the project are was first established:

P00012345 - PMO Project A (literal value = l1)
P00023456 - PMO Project A (literal value = l2)

Then a year later and new enumeration needs to be added as follows:
P00012346 - PMO Project AB (literal value = l3)

If user creates a query and wants to sort on PMO Project attribute, then the results are returned as follows (based on literal value):
P00012345 - PMO Project A (literal value = l1)
P00023456 - PMO Project A (literal value = l2)
P00012346 - PMO Project AB (literal value = l3)

User can not see literal value, and is expecting the results to appear as:
P00012345 - PMO Project A (literal value = l1)
P00012346 - PMO Project AB (literal value = l3)
P00023456 - PMO Project A (literal value = l2)

Does anyone know if this in fact functioning as designed or should this be considered as a defect?  We are currently using RTC 4.0.3.

Thanks for any support/feedback!