On Feb 5, 10:39 pm, Edward Elhauge <[EMAIL PROTECTED]> wrote:
> The only feedback I'd have is that an Edit button would be nice so that
> the Change Properties -> Description textbox section wouldn't take up
> so much room. Alternatively a read-only view of the ticket, with all of
> it's comments, would be solve the same problem. I envision bringing a
> stack of open tickets to a project meeting and going over them one at
> a time to see what it would take to close them.
Here's the "Release Ticket Review" report we use to go over tickets in
meetings:
SELECT
(CASE WHEN t.status='closed' THEN
t.milestone||' ('||t.status||': '||t.resolution||')' ELSE
t.milestone||' ('||t.status||')' END) AS __group__,
id AS ticket, summary, type, reporter, owner AS owner_,
' ' AS sp1, (CASE WHEN sub.value='New' OR sub.value='Other' THEN
component||'.'||sub.value ELSE
sub.value END) AS subcomponent_,
t.description AS _description_,
author||': '||lastcomment AS _comment_
FROM ticket t
INNER JOIN milestone m ON (t.milestone = m.name)
LEFT OUTER JOIN
(SELECT outtc.ticket, outtc.author, outtc.newvalue AS
lastcomment
FROM ticket_change AS outtc
JOIN (SELECT ticket, Max(time) AS lasttime
FROM ticket_change
WHERE field = 'comment' AND newvalue <> ''
GROUP BY ticket) AS intc ON (outtc.time = intc.lasttime)
WHERE outtc.field = 'comment') lc ON (t.id = lc.ticket)
LEFT OUTER JOIN ticket_custom obj ON (t.id = obj.ticket AND
obj.name = 'objects')
LEFT OUTER JOIN ticket_custom sub ON (t.id = sub.ticket AND
sub.name = 'subcomponent')
WHERE m.due <> 0 AND m.completed = 0
ORDER BY m.due, t.status, t.resolution, t.reporter, ticket
It groups tickets by milestone and status, lists some header
information for each ticket, then the description and the last comment
made on the ticket. You can cut out the buisness about objects and
subcomponents if you like; I left them in to illustrate how to include
custom fields, and because I'm lazy :). If you don't need the second
line, you can also remove "Sp1" which is a spacer I added to give the
ticket number some space (makes the report much easier to read). The
report isolates milestones that are open and have a due date because
we a have a milestone for long-term and pie-in-the-sky tickets that we
don't consider on a regular basis.
Oh, and we run trac on postgres, so the SQL syntax may be different
depending on the database you use.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
