Modify

Opened 23 months ago

Closed 22 months ago

Last modified 8 months ago

#10488 closed enhancement (fixed)

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

Reported by: rjollos Owned by: rjollos
Priority: normal Component: TracHacks
Severity: normal Keywords:
Cc: hasienda, osimons, falkb, chrisnelson, jun66j5 Trac Release: 0.10

Description (last modified by rjollos)

#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 Type column.
  • 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.

Attachments (1)

ShowGroup.png (42.1 KB) - added by rjollos 23 months ago.

Download all attachments as: .zip

Change History (15)

Changed 23 months ago by rjollos

comment:1 Changed 23 months ago by rjollos

  • Description modified (diff)

comment:2 in reply to: ↑ description ; follow-up: Changed 22 months ago by falkb

Replying to 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.

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.

comment:3 in reply to: ↑ 2 ; follow-ups: Changed 22 months ago by ChrisNelson

Replying to falkb:

Replying to 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.

:-( 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?

comment:4 in reply to: ↑ description Changed 22 months ago 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.

comment:5 in reply to: ↑ 3 Changed 22 months ago by falkb

Replying to ChrisNelson:

How is this different from #10478?

Ah...very good :)

comment:6 Changed 22 months ago 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) a vs. (b) b

    a b  
    11SELECT p.value AS __color__, 
    2    id AS ticket, summary, component, severity, 
     2   id AS ticket, summary, t.type, r.value AS release, 
     3   component AS __group__, 
    34   (CASE status WHEN 'assigned' THEN owner||' *' ELSE owner END) AS owner, 
    45   time AS created, 
    56   changetime AS modified, description AS _description, 
    67   reporter AS _reporter 
    7   FROM ticket t, enum p 
     8  FROM ticket t 
     9    LEFT OUTER JOIN ticket_custom r 
     10    ON (t.id = r.ticket AND r.name = 'release') 
     11    JOIN enum p ON p.name = t.priority AND p.type='priority' 
    812  WHERE status IN ('new', 'assigned', 'reopened') 
    9   AND component = '$COMPONENT' 
    10 AND p.name = t.priority AND p.type = 'priority' 
     13    AND component = '$COMPONENT' 
    1114  ORDER BY p.value, severity, time 

comment:7 Changed 22 months ago 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:

  • (a) d vs. (b) c

    a b  
    11SELECT p.value AS __color__, 
    2    id AS ticket, summary, component, severity, 
     2   id AS ticket, summary, t.type, r.value AS release, 
     3   component AS __group__, 
    34   (CASE status WHEN 'assigned' THEN owner||' *' ELSE owner END) AS owner, 
    45   time AS created, 
    56   changetime AS modified, description AS _description, 
    67   reporter AS _reporter 
    7   FROM ticket t, enum p 
     8  FROM ticket t 
     9    LEFT OUTER JOIN ticket_custom r 
     10    ON (t.id = r.ticket AND r.name = 'release') 
     11    JOIN enum p ON p.name = t.priority AND p.type='priority' 
    812  WHERE component = '$COMPONENT' 
    9 AND p.name = t.priority AND p.type = 'priority' 
    1013  ORDER BY p.value, severity, time 

comment:8 in reply to: ↑ description Changed 22 months ago by rjollos

Replying to 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?

comment:9 Changed 22 months ago 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.

comment:10 Changed 22 months ago by rjollos

  • Resolution set to fixed
  • Status changed from assigned to closed
  • Trac Release changed from 0.12 to 0.10

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

comment:11 in reply to: ↑ 3 ; follow-up: Changed 21 months ago by rjollos

Replying to ChrisNelson:

Replying to falkb:

Replying to 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.

:-( The other thing I want to see in a report title is $USER. I've never figured out a way to do that.

=> t:#10979

comment:12 in reply to: ↑ 11 Changed 21 months ago by ChrisNelson

Replying to rjollos:

Replying to ChrisNelson:

Replying to falkb:

Replying to 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.

:-( The other thing I want to see in a report title is $USER. I've never figured out a way to do that.

=> t:#10979

Thanks, Ryan.

comment:13 Changed 20 months ago by rjollos

In 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.

Last edited 8 months ago by rjollos (previous) (diff)

comment:14 Changed 15 months ago by rjollos

  • Cc changed from hasienda, osimons, falkb, chrisnelson, jun66j5 to hasienda, osimons, falkb, chrisnelson, jun66j5
  • Description modified (diff)

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.