Changes between Version 1 and Version 2 of TracReports
- Timestamp:
- 2009/12/27 07:22:18 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracReports
v1 v2 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 19 20 A report consists of these basic parts: 20 21 * '''ID''' -- Unique (sequential) identifier … … 29 30 If a column header is a hyperlink (red), click the column you would like to sort by. Clicking the same header again reverses the order. 30 31 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): 34 * id integer PRIMARY KEY 35 * author text 36 * title text 37 * query text 38 * description text 39 Changing the ID changes the shown order and number in the ''Available Reports'' list and the report's perma-link. This is done by running something like: 40 {{{ 41 update report set id=5 where id=3; 42 }}} 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. 46 47 == Navigating Tickets == 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 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)'' 31 51 32 52 == Alternative Download Formats == … … 61 81 The ''ticket'' table has the following columns: 62 82 * id 83 * type 63 84 * time 64 85 * changetime … … 75 96 * summary 76 97 * description 98 * keywords 77 99 78 100 See TracTickets for a detailed description of the column fields. … … 101 123 Example: 102 124 {{{ 103 SELECT id AS ticket,summary FROM ticket WHERE priority= '$PRIORITY'104 }}} 105 106 To assign a value to $PRIORITY when viewing the report, you must define it as an argument in the report URL, leaving out the theleading '$'.125 SELECT id AS ticket,summary FROM ticket WHERE priority=$PRIORITY 126 }}} 127 128 To assign a value to $PRIORITY when viewing the report, you must define it as an argument in the report URL, leaving out the leading '$'. 107 129 108 130 Example: 109 131 {{{ 110 http:// projects.edgewall.com/trac/reports/14?PRIORITY=high132 http://trac.edgewall.org/reports/14?PRIORITY=high 111 133 }}} 112 134 … … 115 137 Example: 116 138 {{{ 117 http:// projects.edgewall.com/trac/reports/14?PRIORITY=high&SEVERITY=critical139 http://trac.edgewall.org/reports/14?PRIORITY=high&SEVERITY=critical 118 140 }}} 119 141 … … 126 148 Example (''List all tickets assigned to me''): 127 149 {{{ 128 SELECT id AS ticket,summary FROM ticket WHERE owner= '$USER'150 SELECT id AS ticket,summary FROM ticket WHERE owner=$USER 129 151 }}} 130 152 … … 145 167 === Automatically formatted columns === 146 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) 147 171 * '''created, modified, date, time''' -- Format cell as a date and/or time. 148 149 172 * '''description''' -- Ticket description field, parsed through the wiki engine. 150 173 … … 153 176 SELECT id as ticket, created, status, summary FROM ticket 154 177 }}} 178 179 Those columns can also be defined but marked as hidden, see [#column-syntax below]. 155 180 156 181 === Custom formatting columns === … … 160 185 * '''`__group__`''' -- Group results based on values in this column. Each group will have its own header and table. 161 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 {{{ 188 #!html 189 <div style="margin-left:7.5em">Defaults: 190 <span style="border: none; color: #333; background: transparent; font-size: 85%; background: #fdc; border-color: #e88; color: #a22">Color 1</span> 191 <span style="border: none; color: #333; background: transparent; font-size: 85%; background: #ffb; border-color: #eea; color: #880">Color 2</span> 192 <span style="border: none; color: #333; background: transparent; font-size: 85%; background: #fbfbfb; border-color: #ddd; color: #444">Color 3</span> 193 <span style="border: none; color: #333; background: transparent; font-size: 85%; background: #e7ffff; border-color: #cee; color: #099">Color 4</span> 194 <span style="border: none; color: #333; background: transparent; font-size: 85%; background: #e7eeff; border-color: #cde; color: #469">Color 5</span> 195 </div> 196 }}} 162 197 * '''`__style__`''' -- A custom CSS style expression to use for the current row. 163 198 … … 177 212 numeric representation from the ''enum'' table. 178 213 179 === Changing layout of report rows === 214 === Changing layout of report rows === #column-syntax 180 215 By default, all columns on each row are display on a single row in the HTML 181 216 report, possibly formatted according to the descriptions above. However, it's … … 187 222 188 223 * '''`_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). 224 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. 189 225 190 226 '''Example:''' ''List active tickets, grouped by milestone, colored by priority, with description and multi-line layout'' … … 209 245 === Reporting on custom fields === 210 246 211 If you have added custom fields to your tickets (experimental feature in v0.8, see TracTicketsCustomFields), you can write a SQL query to cover them. You'll need to make a join on the ticket_custom table, but this isn't especially easy. 212 213 If you have tickets in the database ''before'' you declare the extra fields in trac.ini, there will be no associated data in the ticket_custom table. To get around this, use SQL's "LEFT OUTER JOIN" clauses. See TracIniReportCustomFieldSample for some examples. 214 215 ---- 216 See also: TracTickets, TracQuery, TracGuide 247 If you have added custom fields to your tickets (a feature since v0.8, see TracTicketsCustomFields), you can write a SQL query to cover them. You'll need to make a join on the ticket_custom table, but this isn't especially easy. 248 249 If you have tickets in the database ''before'' you declare the extra fields in trac.ini, there will be no associated data in the ticket_custom table. To get around this, use SQL's "LEFT OUTER JOIN" clauses. See [trac:TracIniReportCustomFieldSample TracIniReportCustomFieldSample] for some examples. 250 251 '''Note that you need to set up permissions in order to see the buttons for adding or editing reports.''' 252 253 ---- 254 See also: TracTickets, TracQuery, TracGuide, [http://www.sqlite.org/lang_expr.html Query Language Understood by SQLite]
