-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
3.5.3
-
3.05
-
Severity 2 - Major
-
1
-
Our project contained several filters that sorted by Issue Type. When we were running 3.3.2, the sort order was whatever order was specified on the Issue Type page. Since upgrading to 3.5.3, we created an Issue Type Scheme for our project specifying the same order. When a user creates a new issue in our project, the order in the pick list is in the specified order. Unfortunately, the filters now sort Issue Type alphabetically instead of by the specified order. Because we use different issue types at each phase of our development lifecycle, this change in behavior has made these filters largely unusable. Is there a way to configure the filters to revert to displaying Issue Types in the order specified as they did in 3.3.2?
- is duplicated by
-
JRASERVER-10058 Sorting by 'Select list' custom field uses option labels instead of option order
- Closed
- is related to
-
JRASERVER-14161 Search result sort order for select-list fields does not respect field order
- Closed
-
JRASERVER-15315 Sorting on Two Dimensional Array Gadget is not Natural
- Closed
- relates to
-
JRASERVER-11563 Sorting of values in statistics is not according to order defined in administration
- Closed