Opened 17 years ago
Closed 17 years ago
#7224 closed defect (duplicate)
"Active Tickets by Milestone" groups tickets incorrectly after upgrade to 0.11rc1
| Reported by: | Owned by: | Matthew Good | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | report system | Version: | 0.11rc1 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I recently upgraded Trac to 0.11rc1 using easy_install.
Afterwards, when I run my favorite report "Active Tickets by Milestone", instead of each Milestone having its own group of tickets, each Milestone/Priority combination has a box.
For example, "Milestone 1" has a group for "Minor" priority, and another for "Major".
This is the query:
SELECT p.value AS __color__, concat(milestone, ' Release') AS __group__, id AS ticket, summary, priority, t.type AS type, owner, status, time AS created, changetime AS _changetime, description AS _description, reporter AS _reporter FROM ticket t LEFT JOIN enum p ON p.name = t.priority AND p.type = 'priority' WHERE status <> 'closed' ORDER BY (milestone IS NULL),milestone, p.value, t.type, time
If I remove the
p.value as __color__
I get this error:
Report execution failed: (1054, "Unknown column '0' in 'order clause'")
Thanks for any help or clarifications you can provide!
System Info
Debian "Testing" 2.6.24
Python 2.5.2
MySql 5.0.51a-5 (Debian package)



Yes, we're aware of the problem, see #7179.