Opened 8 years ago
Last modified 8 years ago
#12402 closed defect
Query system doesn't respect order of ticket types — at Version 1
Reported by: | Jun Omae | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 1.0.11 |
Component: | query system | Version: | |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
The following query is generated from query:?owner=admin&order=type
. The ticket types are defined in enum
table and have the order.
However, the query doesn't sort by enum.value
. If resolution
, priority
and severity
, it sorts by enum.value
.
SELECT t.id AS id,t.summary AS summary,t.owner AS owner,t.type AS type,t.status AS st atus,t.priority AS priority,t.milestone AS milestone,t.time AS time,t.changetime AS changetime,t.reporter AS reporter,priority.value AS priority_value FROM ticket AS t LEFT OUTER JOIN enum AS priority ON (priority.type='priority' AND priority.name=priority) WHERE ((COALESCE(t.reporter,'')=%s)) ORDER BY COALESCE(t.type,'')='',t.type,t.id
Note:
See TracTickets
for help on using tickets.