{14} Tickets closed in the last week (or so) (dates in UTC)

For discussions which are not directly related to MythTV.

Moderator: Forum Moderators

Post Reply
bdrhoa
Newcomer
Posts: 2
Joined: Mon Apr 14, 2014 5:21 pm
United States of America

{14} Tickets closed in the last week (or so) (dates in UTC)

Post by bdrhoa » Mon Apr 14, 2014 5:23 pm

Could you please share the code for the Trac report {14} Tickets closed in the last week (or so) (dates in UTC) (9 matches)?

User avatar
rwagner
Developer
Posts: 217
Joined: Thu Feb 06, 2014 11:37 pm
United States of America

Re: {14} Tickets closed in the last week (or so) (dates in U

Post by rwagner » Mon Apr 14, 2014 7:34 pm

SELECT p.value AS __color__,
'Closed '||STRFTIME('%m-%d', c.time/1000000, 'unixepoch') AS __group__,
(CASE t.status WHEN 'assigned' THEN 'font-size: 18pt !important; font-weight: bold !important;' ELSE '' END) AS __style__,
c.author AS "closed by",
milestone AS "when",
resolution,
id AS ticket,
(CASE t.status WHEN 'assigned' THEN '* ' ELSE '' END) || summary AS summary,
keywords,
component,
t.type AS type,
severity,
STRFTIME("%Y-%m-%d", t.time/1000000, "unixepoch") AS opened,
ROUND((c.time-t.time)/1000000/(60*60*24))||' days' AS age
FROM ticket t, enum p, ticket_change c
WHERE t.id=c.ticket
AND c.field LIKE "status%" -- wtf, a straignt ="status" match fails!?
AND c.newvalue="closed"
AND (strftime('%s', 'now') - c.time/1000000) <= (60 * 60 * 24 * 8)
AND p.name = t.priority
AND p.type = 'priority'
GROUP BY t.id
ORDER BY STRFTIME('%Y-%m-%d', c.time/100000, 'unixepoch') DESC,
c.author,
t.id

bdrhoa
Newcomer
Posts: 2
Joined: Mon Apr 14, 2014 5:21 pm
United States of America

Re: {14} Tickets closed in the last week (or so) (dates in U

Post by bdrhoa » Tue Apr 15, 2014 5:21 pm

Thank you!

Post Reply