Changes between Version 3 and Version 4 of TracReports
- Timestamp:
- 24/11/16 03:15:40 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracReports
v3 v4 30 30 31 31 == Changing Report Numbering == 32 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)'':32 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: 33 33 * id integer PRIMARY KEY 34 34 * author text … … 47 47 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. 48 48 49 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)''49 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). 50 50 51 51 == Alternative Download Formats == … … 109 109 }}} 110 110 111 Dynamic variables can also be used in the report title and description (since 1.1.1). 111 112 112 113 == Advanced Reports: Dynamic Variables == … … 136 137 }}} 137 138 138 Dynamic variables can also be used in the report title and description (since 1.1.1).139 139 140 140 === !Special/Constant Variables === … … 164 164 * '''id''' — same as '''ticket''' above when '''realm''' is not set 165 165 * '''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) 166 - for some kind of resources, it may be necessary to specify their ''parent'' resources (e.g. for ''changeset'', which ''repos'') and this can be achieved using the '''parent_realm''' and '''parent_id''' columns 166 167 * '''created, modified, date, time''' — Format cell as a date and/or time. 167 168 * '''description''' — Ticket description field, parsed through the wiki engine. … … 245 246 === Reporting on custom fields === 246 247 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 If you have added custom fields to your tickets (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 249 250 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.
