# Ticket #10488 (closed enhancement: fixed)

Opened 7 months ago

## Modify columns shown in reports {9} and {10}

Reported by: Assigned to: rjollos rjollos normal TracHacks normal hasienda, osimons, falkb, chrisnelson, jun66j5 0.10

#10478 has me thinking about the information we show in the most commonly used reports {9} and {10}. I've wanted Type and Trac Release to be shown as columns on that report. I believe those are far more useful to most developers than Severity and Component.

Component information could be shown by making the change component AS __group__, so that the Component displays in the report, but not as a column, rather as shown in the screen capture (for which Component=TracHacks). I was trying to find a way to show the Component in the report title or description, but couldn't find a way to do that. Does anyone know a way (whether it be in Trac 0.10 or later)?

So I open this ticket to request feedback on making the following changes to reports {9} and {10}:

• Add the Trac Release column.
• Don't show the Severity column.
• Don't show the Component column, and group by component.

We could also consider deleting or replacing reports {3} and {6}, since milestones aren't used on t-h.o.

## Change History

### 10/16/12 02:04:15 changed by rjollos

• description changed.

### (in reply to: ↑ description ; follow-up: ↓ 3 ) 10/16/12 13:29:59 changed by falkb

... a way to show the Component in the report title or description, but couldn't find a way to do that. Does anyone know a way (whether it be in Trac 0.10 or later)?

I think it's not possible.

So I open this ticket to request feedback on making the following changes to reports {9} and {10}: * Add the Type column. * Add the Trac Release column. * Don't show the Severity column. * Don't show the Component column, and group by component.

### (in reply to: ↑ 2 ; follow-ups: ↓ 5 ↓ 11 ) 10/16/12 14:16:01 changed by ChrisNelson

... a way to show the Component in the report title or description, but couldn't find a way to do that. Does anyone know a way (whether it be in Trac 0.10 or later)?

I think it's not possible.

:-( The other thing I want to see in a report title is $USER. I've never figured out a way to do that. So I open this ticket to request feedback on making the following changes to reports {9} and {10}: * Add the Type column. * Add the Trac Release column. * Don't show the Severity column. * Don't show the Component column, and group by component. As activity indicator, I'd be interested in the ticket's 'Last Modified' datetime as additional column. How is this different from #10478? ### (in reply to: ↑ description ) 10/16/12 14:16:59 changed by ChrisNelson Replying to rjollos: ... So I open this ticket to request feedback on making the following changes to reports {9} and {10}: * Add the Type column. * Add the Trac Release column. * Don't show the Severity column. * Don't show the Component column, and group by component. ... I don't care about the Trac Release but it takes up so little room I won't vote against it. The other changes are good, I think. ### (in reply to: ↑ 3 ) 10/16/12 14:18:23 changed by falkb Replying to ChrisNelson: How is this different from #10478? Ah...very good :) ### 10/18/12 20:27:36 changed by rjollos • owner changed from otaku42 to rjollos. • status changed from new to assigned. Here is the new report {9}: SELECT p.value AS __color__, id AS ticket, summary, t.type, r.value AS release, component AS __group__, (CASE status WHEN 'assigned' THEN owner||' *' ELSE owner END) AS owner, time AS created, changetime AS modified, description AS _description, reporter AS _reporter FROM ticket t LEFT OUTER JOIN ticket_custom r ON (t.id = r.ticket AND r.name = 'release') JOIN enum p ON p.name = t.priority AND p.type='priority' WHERE status IN ('new', 'assigned', 'reopened') AND component = '$COMPONENT'
ORDER BY p.value, severity, time


And here is the diff:

--- a   2012-10-18 10:47:58.432437400 -0700
+++ b   2012-10-18 11:24:52.381068000 -0700
@@ -1,11 +1,14 @@
SELECT p.value AS __color__,
-   id AS ticket, summary, component, severity,
+   id AS ticket, summary, t.type, r.value AS release,
+   component AS __group__,
(CASE status WHEN 'assigned' THEN owner||' *' ELSE owner END) AS owner,
time AS created,
changetime AS modified, description AS _description,
reporter AS _reporter
-  FROM ticket t, enum p
+  FROM ticket t
+    LEFT OUTER JOIN ticket_custom r
+    ON (t.id = r.ticket AND r.name = 'release')
+    JOIN enum p ON p.name = t.priority AND p.type='priority'
WHERE status IN ('new', 'assigned', 'reopened')
-  AND component = '$COMPONENT' -AND p.name = t.priority AND p.type = 'priority' + AND component = '$COMPONENT'
ORDER BY p.value, severity, time


### 10/18/12 20:36:00 changed by rjollos

Here is the new report {10}:

SELECT p.value AS __color__,
id AS ticket, summary, t.type, r.value AS release,
(CASE status WHEN 'assigned' THEN owner||' *' ELSE owner END) AS owner,
time AS created,
changetime AS modified, description AS _description,
reporter AS _reporter
FROM ticket t
LEFT OUTER JOIN ticket_custom r
ON (t.id = r.ticket AND r.name = 'release')
JOIN enum p ON p.name = t.priority AND p.type='priority'
WHERE component = '$COMPONENT' ORDER BY p.value, severity, time  And here is the diff: --- d 2012-10-18 11:31:02.968264400 -0700 +++ c 2012-10-18 11:34:19.894527900 -0700 @@ -1,11 +1,13 @@ SELECT p.value AS __color__, - id AS ticket, summary, component, severity, + id AS ticket, summary, t.type, r.value AS release, + component AS __group__, (CASE status WHEN 'assigned' THEN owner||' *' ELSE owner END) AS owner, time AS created, changetime AS modified, description AS _description, reporter AS _reporter - FROM ticket t, enum p + FROM ticket t + LEFT OUTER JOIN ticket_custom r + ON (t.id = r.ticket AND r.name = 'release') + JOIN enum p ON p.name = t.priority AND p.type='priority' WHERE component = '$COMPONENT'
-AND p.name = t.priority AND p.type = 'priority'
ORDER BY p.value, severity, time


### (in reply to: ↑ description ) 10/18/12 20:58:22 changed by rjollos

... Component information could be shown by making the change component AS __group__, ...

By doing this, we lose the ability to sort by column (TracReports#ChangingSortOrder). It looks like there is a way in later versions of Trac (t:TracReports#rewriting) to allow sorting by column even when tickets are grouped, but I don't see a way to do it in Trac 0.10. Any suggestions?

### 10/18/12 21:03:05 changed by rjollos

I do think we need the ability to sort these reports, but I'll leave the reports as is to see if anyone has feedback on this today.

### 10/20/12 06:09:06 changed by rjollos

• release changed from 0.12 to 0.10.
• status changed from assigned to closed.
• resolution set to fixed.

I went back to showing the Component as a column for now, and opened ticket #10510 for some modifications to make when we get on Trac 1.0.

{9}:

SELECT p.value AS __color__,
id AS ticket, summary, component, t.type, r.value AS release,
(CASE status WHEN 'assigned' THEN owner||' *' ELSE owner END) AS owner,
time AS created,
changetime AS modified, description AS _description,
reporter AS _reporter
FROM ticket t
LEFT OUTER JOIN ticket_custom r
ON (t.id = r.ticket AND r.name = 'release')
JOIN enum p ON p.name = t.priority AND p.type='priority'
WHERE status IN ('new', 'assigned', 'reopened')
AND component = '$COMPONENT' ORDER BY p.value, severity, time  {10}: SELECT p.value AS __color__, id AS ticket, summary, component, t.type, r.value AS release, (CASE status WHEN 'assigned' THEN owner||' *' ELSE owner END) AS owner, time AS created, changetime AS modified, description AS _description, reporter AS _reporter FROM ticket t LEFT OUTER JOIN ticket_custom r ON (t.id = r.ticket AND r.name = 'release') JOIN enum p ON p.name = t.priority AND p.type='priority' WHERE component = '$COMPONENT'
ORDER BY p.value, severity, time


### (in reply to: ↑ 3 ; follow-up: ↓ 12 ) 12/11/12 00:32:29 changed by rjollos

... a way to show the Component in the report title or description, but couldn't find a way to do that. Does anyone know a way (whether it be in Trac 0.10 or later)?

I think it's not possible.

=> t:#10979

Thanks, Ryan.

### 01/06/13 17:35:00 changed by rjollos

I case you haven't been following the ticket, the patch I submitted has been scheduled for a 1.1.x development release, so the feature will be available in production release 1.2.

### Add/Change #10488 (Modify columns shown in reports {9} and {10})

Change Properties