Changes between Version 3 and Version 4 of 0.12/TracReports
- Timestamp:
- Mar 30, 2010, 1:55:50 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
0.12/TracReports
v3 v4 31 31 32 32 == 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):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 ''(since 0.10)'': 34 34 * id integer PRIMARY KEY 35 35 * author text … … 48 48 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 49 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)''50 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 51 52 52 == Alternative Download Formats == … … 57 57 === Comma-delimited - CSV (Comma Separated Values) === 58 58 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.59 '''Note:''' The output is fully escaped so carriage returns, line feeds, and commas will be preserved in the output. 60 60 61 61 === Tab-delimited === … … 73 73 A report is basically a single named SQL query, executed and presented by 74 74 Trac. Reports can be viewed and created from a custom SQL expression directly 75 in fromthe web interface.75 in the web interface. 76 76 77 77 Typically, a report consists of a SELECT-expression from the 'ticket' table, … … 100 100 See TracTickets for a detailed description of the column fields. 101 101 102 '''all active tickets, sorted by priority and time''' 103 104 '''Example:''' ''All active tickets, sorted by priority and time'' 102 Example: '''All active tickets, sorted by priority and time''' 105 103 {{{ 106 104 SELECT id AS ticket, status, severity, priority, owner, … … 110 108 }}} 111 109 112 113 ---- 114 110 --- 115 111 116 112 == Advanced Reports: Dynamic Variables == … … 141 137 142 138 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.139 === !Special/Constant Variables === 140 There is one dynamic variable whose value is set automatically (the URL does not have to be changed) to allow practical reports. 145 141 146 142 * $USER -- Username of logged in user. … … 178 174 179 175 Those columns can also be defined but marked as hidden, see [#column-syntax below]. 176 177 See trac:wiki/CookBook/Configuration/Reports for some example of creating reports for realms other than ''ticket''. 180 178 181 179 === Custom formatting columns ===
