Enhanced Query for All Tickets by Milestone + RFE for a new automatically detected datatype

[Carsten Klein]

The below query orders all milestones and tickets by their respective due date or the time of creation in case of the ticket, as was implemented before.

It would be nice to have a DUE datatype being mapped to the datetime datatype in order for displaying the due date in the __group__ header along with the t.milestone name.

TIA

Carsten

---

SELECT p.value AS __color__,
   t.milestone ||' Release' AS __group__,
   t.id AS ticket, t.summary, t.component, t.version, t.type AS type, 
   (CASE status WHEN 'assigned' THEN t.owner||' *' ELSE t.owner END) AS owner,
   t.time AS created, m.due as date,
   t.changetime AS _changetime, t.description AS _description,
   t.reporter AS _reporter
  FROM ticket t
  LEFT JOIN enum p ON p.name = t.priority AND p.type = 'priority'
  LEFT JOIN milestone m ON m.name = milestone
  WHERE status IN ('new', 'assigned', 'reopened') 
  ORDER BY (milestone IS NULL),m.due, p.value, t.type, time

[Christian Boos]

Some kind of type annotation for columns, or more generally, output filters, could be useful.