Changes between Version 2 and Version 3 of TracReports
- Timestamp:
- Dec 2, 2009, 12:07:59 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracReports
v2 v3 17 17 ''This will make the query module the default handler for the “View Tickets” navigation item. We encourage you to try this configuration and report back what kind of features of reports you are missing, if any.'' 18 18 19 '''''You will almost definitely need to restart your httpd at this point.'''''20 19 21 20 A report consists of these basic parts: … … 43 42 }}} 44 43 Keep in mind that the integrity has to be maintained (i.e., ID has to be unique, and you don't want to exceed the max, since that's managed by SQLite someplace). 44 45 You may also need to update or remove the report number stored in the report or query. 45 46 46 47 == Navigating Tickets == … … 166 167 === Automatically formatted columns === 167 168 * '''ticket''' -- Ticket ID number. Becomes a hyperlink to that ticket. 169 * '''id''' -- same as '''ticket''' above when '''realm''' is not set 170 * '''realm''' -- together with '''id''', can be used to create links to other resources than tickets (e.g. a realm of ''wiki'' and an ''id'' to a page name will create a link to that wiki page) 168 171 * '''created, modified, date, time''' -- Format cell as a date and/or time. 169 170 172 * '''description''' -- Ticket description field, parsed through the wiki engine. 171 173 … … 174 176 SELECT id as ticket, created, status, summary FROM ticket 175 177 }}} 178 179 Those columns can also be defined but marked as hidden, see [#column-syntax below]. 176 180 177 181 === Custom formatting columns === … … 180 184 181 185 * '''`__group__`''' -- Group results based on values in this column. Each group will have its own header and table. 186 * '''`__grouplink__`''' -- Make the header of each group a link to the specified URL. The URL is taken from the first row of each group. 182 187 * '''`__color__`''' -- Should be a numeric value ranging from 1 to 5 to select a pre-defined row color. Typically used to color rows by issue priority. 183 188 {{{ … … 193 198 * '''`__style__`''' -- A custom CSS style expression to use for the current row. 194 199 195 '''Example:''' ''List active tickets, grouped by milestone, colored by priority''200 '''Example:''' ''List active tickets, grouped by milestone, group header linked to milestone page, colored by priority'' 196 201 {{{ 197 202 SELECT p.value AS __color__, 198 203 t.milestone AS __group__, 204 '../milestone/' || t.milestone AS __grouplink__, 199 205 (CASE owner WHEN 'daniel' THEN 'font-weight: bold; background: red;' ELSE '' END) AS __style__, 200 206 t.id AS ticket, summary … … 208 214 numeric representation from the ''enum'' table. 209 215 210 === Changing layout of report rows === 216 === Changing layout of report rows === #column-syntax 211 217 By default, all columns on each row are display on a single row in the HTML 212 218 report, possibly formatted according to the descriptions above. However, it's … … 218 224 219 225 * '''`_column`''' -- ''Hide data''. Prepending an underscore ('_') to a column name instructs Trac to hide the contents from the HTML output. This is useful for information to be visible only if downloaded in other formats (like CSV or RSS/XML). 226 This can be used to hide any kind of column, even important ones required for identifying the resource, e.g. `id as _id` will hide the '''Id''' column but the link to the ticket will be present. 220 227 221 228 '''Example:''' ''List active tickets, grouped by milestone, colored by priority, with description and multi-line layout''