Modify ↓
#10510 closed enhancement (fixed)
Remove Component column from reports {9} and {10}
| Reported by: | Ryan J Ollos | Owned by: | Ryan J Ollos |
|---|---|---|---|
| Priority: | normal | Component: | TracHacks |
| Severity: | normal | Keywords: | |
| Cc: | Michael Renzmann, Steffen Hoffmann, osimons | Trac Release: | 1.0 |
Description (last modified by )
When on Trac 1.0, we should be able to make the following untested modifications to reports {9} and {10}, which will remove the Component column, group the tickets by Component and still allow the report to be sorted by any column.
component->component AS __group__ORDER BY p.value, severity, time->ORDER BY __group__, @SORT_COLUMN@, p.value, severity, time
Attachments (4)
Change History (10)
comment:1 Changed 13 years ago by
| Trac Release: | 0.12 → 1.0 |
|---|
comment:2 Changed 12 years ago by
comment:3 Changed 12 years ago by
| Status: | new → assigned |
|---|
comment:4 Changed 12 years ago by
| Description: | modified (diff) |
|---|
Changed 12 years ago by
Changed 12 years ago by
| Attachment: | Before.png added |
|---|
Changed 12 years ago by
| Attachment: | Report9After.png added |
|---|
Changed 12 years ago by
| Attachment: | Report9-Before.png added |
|---|
comment:5 Changed 12 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
The changes in comment:description had already been made. Additional, a link to the project wiki page was added as a __grouplink__. The reports are now:
SELECT p.value AS __color__, id AS ticket, summary, '/wiki/' || component AS __grouplink__, component AS __group__, t.type, r.value AS release, owner, status, 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 <> 'closed' AND component = '$COMPONENT' ORDER BY __group__, @SORT_COLUMN@, p.value, severity, time
SELECT p.value AS __color__, id AS ticket, summary, '/wiki/' || component AS __grouplink__, component AS __group__, t.type, r.value AS release, owner, status, 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 __group__, status, @SORT_COLUMN@, p.value, severity, time
In the future we'll be able to group report {10} by status, but a Trac upgrade will be needed first: #11464.
comment:6 Changed 12 years ago by
Report {10} was not sorting by ticket id, so I made the following change:
- ORDER BY __group__, status, @SORT_COLUMN@, p.value, severity, time + ORDER BY __group__, @SORT_COLUMN@, p.value, severity, time
Note: See
TracTickets for help on using
tickets.



Report {10} should also group by status (see comment:61:ticket:10193).