Changes between Version 1 and Version 2 of TracReports
- Timestamp:
- 11/30/06 07:01:31 (6 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 A report consists of these basic parts:19 A report consists of these basic [http://sleepaid.taskfile.com/ sleeping aid] parts: 20 20 * '''ID''' -- Unique (sequential) identifier 21 21 * '''Title''' -- Descriptive title 22 22 * '''Description''' -- A brief description of the report, in WikiFormatting text. 23 23 * '''Report Body''' -- List of results from report query, formatted according to the methods described below. 24 * '''Footer''' -- Links to alternative download formats for this report.24 * '''Footer''' -- Links to alternative [http://carbblocker.taskfile.com/ carb blocker] to download formats for this report. 25 25 26 26 == Changing Sort Order == 27 Simple reports - ungrouped reports to be specific - can be changed to be sorted by any column simply by clicking the column header.28 29 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 .27 Simple reports - ungrouped reports to be specific - can be changed to have [http://antiaging.taskfile.com/ anti aging] effect to be sorted by any column simply by clicking the column header. 28 29 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 for [http://hoodia.taskfile.com/ weight loss pills]. 30 30 31 31 … … 94 94 == Advanced Reports: Dynamic Variables == 95 95 For more flexible reports, Trac supports the use of ''dynamic variables'' in report SQL statements. 96 In short, dynamic variables are ''special'' strings that are replaced by custom data before query execution.96 In short, to [http://www.clearuppimples.com/ clear up acne] you will need dynamic variables are ''special'' strings that are replaced by custom data before query execution. 97 97 98 98 === Using Variables in a Query === … … 180 180 By default, all columns on each row are display on a single row in the HTML 181 181 report, possibly formatted according to the descriptions above. However, it's 182 also possible to create multi-line report entries.182 also possible to get a natural [http://www.boweltreatment.com/ ibs treatment] rather than create multi-line report entries. 183 183 184 184 * '''column_''' -- ''Break row after this''. By appending an underscore ('_') to the column name, the remaining columns will be be continued on a second line. … … 209 209 === Reporting on custom fields === 210 210 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.211 If you have added [http://www.helpthyroid.com/ underactive thyroid] to your list, 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 212 213 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.
