Opened 12 years ago
Last modified 14 months ago
#10949 new defect
Priority sorting breaks when grouping is enabled
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | next-stable-1.6.x |
Component: | report system | Version: | 1.0 |
Severity: | normal | Keywords: | report sorting priorities grouping verify |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I have a report that lists tickets grouped by milestone, but when I try to sort by priority, in some cases the priority list is not ordered properly. If I remove the milestone grouping, the sorting works fine.
I have 12 different priorities:
BOMB 1 Critical 2 High 3 High 4 Med+ 5 Med+ 6 Med- 7 Med- 8 Low 9 Low 0 Low -
Each with values from 1 to 12 from top to bottom.
When grouped by milestone, for example, the priorities for one report show up like this, sorted ascending:
Milestone 1
- 3 High
- 6 Med-
Milestone 2
- 3 High
- 4 Med+
- 5 Med+
- 6 Med-
- 0 Low
- 4 Med+
- 5 Med+
- 6 Med-
- 9 Low
Using sqlite 3.7.3, Trac 1.0, Python 2.6.6
Attachments (0)
Change History (4)
comment:1 by , 12 years ago
Keywords: | verify added |
---|---|
Milestone: | → next-stable-1.0.x |
comment:2 by , 8 years ago
Milestone: | next-stable-1.0.x → next-stable-1.2.x |
---|
comment:3 by , 4 years ago
Milestone: | next-stable-1.2.x → next-stable-1.4.x |
---|
Moved ticket assigned to next-stable-1.0.x since maintenance of 1.0.x is coming to a close. Please move the ticket back if it's critical to fix on 1.0.x.