Opened 14 years ago
Last modified 9 years ago
#9505 new enhancement
Missing feature from ticket query module: color tickets based on contents of field
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | unscheduled |
Component: | ticket system | Version: | |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Note: The report module is being phased out in its current form because it seriously limits the ability of the Trac team to make adjustments to the underlying database schema. We believe that the query module is a good replacement that provides more flexibility and better usability. While there are certain reports that cannot yet be handled by the query module, we intend to further enhance it so that at some point the reports module can be completely removed. This also means that there will be no major enhancements to the report module anymore.
I think that a missing feature is the ability to color tickets based on values. For example, you can color tickets red that have the priority of "blocker".
If this already exists, could you please provide some documentation on how to accomplish this query?
Attachments (0)
Change History (5)
comment:1 by , 14 years ago
Component: | general → ticket system |
---|---|
Milestone: | → unscheduled |
follow-up: 4 comment:2 by , 14 years ago
Thanks for getting back to me so quickly! Would it be possible to contribute code to the Trac development and add color support to the query system?
comment:4 by , 14 years ago
Replying to anonymous:
Thanks for getting back to me so quickly! Would it be possible to contribute code to the Trac development and add color support to the query system?
Certainly! The most difficult part is probably finding a good way to display the functionality to the user.
comment:5 by , 9 years ago
I found a way to get the color that I wanted in the results of the TicketQuery macro. I copied the table.tickets ...
lines out of the report.css and pasted them to the end of the trac.css. The lines I copied are shown below. This may not be the ultimate solution, but it is a workaround for those who really want it.
/* Query results table */ table.tickets tbody tr.added td { font-weight: bold } table.tickets tbody tr.changed td { font-style: italic } table.tickets tbody tr.removed td { color: #999 } table.tickets tbody tr.prio1 { background: #fdc; border-color: #e88 } table.tickets tbody tr.even.prio1 { background: #fed; border-color: #e99 } table.tickets tbody tr.prio2 { background: #ffb; border-color: #eea } table.tickets tbody tr.even.prio2 { background: #ffd; border-color: #dd8 } table.tickets tbody tr.prio3 { background: #fbfbfb; border-color: #ddd } table.tickets tbody tr.even.prio3 { background: #f6f6f6; border-color: #ccc } table.tickets tbody tr.prio4 { background: #e7ffff; border-color: #cee } table.tickets tbody tr.even.prio4 { background: #dff; border-color: #bee } table.tickets tbody tr.prio5 { background: #e7eeff; border-color: #cde } table.tickets tbody tr.even.prio5 { background: #dde7ff } table.tickets tbody tr.prio6 { background: #f0f0f0; border-color: #ddd } table.tickets tbody tr.even.prio6 { background: #f7f7f7 } table.tickets tbody tr.fullrow th { border: none; vertical-align: middle; text-align: center; font-size: 85%; }
We should really reword that section in the docs. While we encourage using the query module as much as possible, the report module isn't going away anytime soon.
No, the coloring functionality in the query doesn't exist yet.