Changes between Version 2 and Version 3 of TracReports
- Timestamp:
- 11/18/04 18:02:59 (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracReports
v2 v3 1 1 = Trac Reports = 2 [[TracGuideToc]] 3 2 4 The Trac reports module provides a simple, yet powerful reporting facility 3 for presenting information about tickets fromthe Trac database.5 to present information about tickets in the Trac database. 4 6 5 Rather than have its own report format, TracReports relies on standard SQL7 Rather than have its own report definition format, TracReports relies on standard SQL 6 8 SELECT statements for custom report definition. 7 9 … … 12 14 * Report Body -- List of results from report query, formatted according to the methods described below. 13 15 * Footer -- Links to alternative download formats for this report. 16 17 18 == Changing Sort Order == 19 Simple reports - ungrouped reports to be specific - can be changed to be sorted by any column simply by clicking the column header. 20 21 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. 14 22 15 23 … … 29 37 All reports support syndication using XML/RSS 2.0. To subscribe to a , click the the orange 'XML' icon at the bottom of the page. See TracRss for general information on RSS support in Trac. 30 38 31 == Changing Sort Order ==32 Simple reports - ungrouped reports to be specific - can be changed to be sorted by any column simply by clicking the column header.33 34 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.35 36 39 ---- 37 40 == Creating Custom Reports == 38 41 39 Creating a custom report requires knowing and using the SQL query language. 42 ''Creating a custom report requires a comfortable knowledge of SQL.'' 40 43 41 44 A report is basically a single named SQL query, executed and presented by … … 128 131 * '''ticket''' -- Ticket ID number. Becomes a hyperlink to that ticket. 129 132 * '''created, modified, date, time''' -- Format cell as a date and/or time. 133 130 134 * '''description''' -- Ticket description field, parsed through the wiki engine. 131 135 … … 136 140 137 141 === Custom formatting columns === 138 Columns whose name begins and ends with '__' (Example: '''__color__''') are142 Columns whose names begin and end with 2 underscores (Example: '''_''''''_color_''''''_''') are 139 143 assumed to be ''formatting hints'', affecting the appearance of the row. 140 144 141 * '''_ __group___''' -- Group results based on values in this column. Each group will have its own header and table.142 * '''_ __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.143 * '''_ __style___''' --- A custom CSS style expression to use for the current row.145 * '''_''''''_group_''''''_''' -- Group results based on values in this column. Each group will have its own header and table. 146 * '''_''''''_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. 147 * '''_''''''_style_''''''_''' -- A custom CSS style expression to use for the current row. 144 148 145 149 '''Example:''' ''List active tickets, grouped by milestone, colored by priority'' … … 190 194 191 195 ---- 192 See also: TracTickets, Trac Guide196 See also: TracTickets, TracQuery, TracGuide
