Changes between Version 44 and Version 45 of TracReports
- Timestamp:
- Apr 10, 2010, 6:45:51 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracReports
v44 v45 1 ** Note: this page documents the 0.12 version of Trac, see [[0.11/TracReports]] if you need the previous version ** 1 2 = Trac Reports = 2 3 [[TracGuideToc]] … … 31 32 32 33 == Changing Report Numbering == 33 There may be instances where you need to change the ID of the report, perhaps to organize the reports better. At present this requires changes to the trac database. The ''report'' table has the following schema (as of 0.10):34 There may be instances where you need to change the ID of the report, perhaps to organize the reports better. At present this requires changes to the trac database. The ''report'' table has the following schema ''(since 0.10)'': 34 35 * id integer PRIMARY KEY 35 36 * author text … … 48 49 Clicking on one of the report results will take you to that ticket. You can navigate through the results by clicking the ''Next Ticket'' or ''Previous Ticket'' links just below the main menu bar, or click the ''Back to Report'' link to return to the report page. 49 50 50 You can safely edit any of the tickets and continue to navigate through the results using the Next/Previous/Back to Reportlinks after saving your results, but when you return to the report, there will be no hint about what has changed, as would happen if you were navigating a list of tickets obtained from a query (see TracQuery#NavigatingTickets). ''(since 0.11)''51 You can safely edit any of the tickets and continue to navigate through the results using the ''!Next/Previous/Back to Report'' links after saving your results, but when you return to the report, there will be no hint about what has changed, as would happen if you were navigating a list of tickets obtained from a query (see TracQuery#NavigatingTickets). ''(since 0.11)'' 51 52 52 53 == Alternative Download Formats == … … 57 58 === Comma-delimited - CSV (Comma Separated Values) === 58 59 Export the report as plain text, each row on its own line, columns separated by a single comma (','). 59 '''Note:''' Carriage returns, line feeds, and commas are stripped from column data to preserve the CSV structure.60 '''Note:''' The output is fully escaped so carriage returns, line feeds, and commas will be preserved in the output. 60 61 61 62 === Tab-delimited === … … 73 74 A report is basically a single named SQL query, executed and presented by 74 75 Trac. Reports can be viewed and created from a custom SQL expression directly 75 in fromthe web interface.76 in the web interface. 76 77 77 78 Typically, a report consists of a SELECT-expression from the 'ticket' table, … … 100 101 See TracTickets for a detailed description of the column fields. 101 102 102 '''all active tickets, sorted by priority and time''' 103 104 '''Example:''' ''All active tickets, sorted by priority and time'' 103 Example: '''All active tickets, sorted by priority and time''' 105 104 {{{ 106 105 SELECT id AS ticket, status, severity, priority, owner, … … 110 109 }}} 111 110 112 113 ---- 114 111 --- 115 112 116 113 == Advanced Reports: Dynamic Variables == … … 141 138 142 139 143 === Special/Constant Variables ===144 There is one ''magic'' dynamic variable to allow practical reports, its value automatically set without having to change the URL.140 === !Special/Constant Variables === 141 There is one dynamic variable whose value is set automatically (the URL does not have to be changed) to allow practical reports. 145 142 146 143 * $USER -- Username of logged in user. … … 179 176 Those columns can also be defined but marked as hidden, see [#column-syntax below]. 180 177 178 See trac:wiki/CookBook/Configuration/Reports for some example of creating reports for realms other than ''ticket''. 179 181 180 === Custom formatting columns === 182 181 Columns whose names begin and end with 2 underscores (Example: '''`__color__`''') are … … 184 183 185 184 * '''`__group__`''' -- Group results based on values in this column. Each group will have its own header and table. 185 * '''`__grouplink__`''' -- Make the header of each group a link to the specified URL. The URL is taken from the first row of each group. 186 186 * '''`__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. 187 187 {{{ … … 197 197 * '''`__style__`''' -- A custom CSS style expression to use for the current row. 198 198 199 '''Example:''' ''List active tickets, grouped by milestone, colored by priority''199 '''Example:''' ''List active tickets, grouped by milestone, group header linked to milestone page, colored by priority'' 200 200 {{{ 201 201 SELECT p.value AS __color__, 202 202 t.milestone AS __group__, 203 '../milestone/' || t.milestone AS __grouplink__, 203 204 (CASE owner WHEN 'daniel' THEN 'font-weight: bold; background: red;' ELSE '' END) AS __style__, 204 205 t.id AS ticket, summary
