Changes between Initial Version and Version 1 of TracReports

Jun 8, 2005, 12:11:56 PM (17 years ago)



  • TracReports

    v1 v1  
     1= Trac Reports =
     4The Trac reports module provides a simple, yet powerful reporting facility
     5to present information about tickets in the Trac database.
     7Rather than have its own report definition format, TracReports relies on standard SQL
     8SELECT statements for custom report definition.
     10A report consists of these basic parts:
     11 * ID -- Unique (sequential) identifier
     12 * Title  -- Descriptive title
     13 * Description  -- A brief description of the report, in WikiFormatting text.
     14 * Report Body -- List of results from report query, formatted according to the methods described below.
     15 * Footer -- Links to alternative download formats for this report.
     18== Changing Sort Order ==
     19Simple reports - ungrouped reports to be specific - can be changed to be sorted by any column simply by clicking the column header.
     21If a column header is a hyperlink (red), click the column you would like to sort by. Clicking the same header again reverses the order.
     24== Alternate Download Formats ==
     25Aside from the default HTML view, reports can also be exported in a number of alternate formats.
     26At the bottom of the report page, you will find a list of available data formats. Click the desired link to
     27download the alternate report format.
     29=== Comma-delimited - CSV (Comma Separated Values) ===
     30Export the report as plain text, each row on its own line, columns separated by a single comma (',').
     31'''Note:''' Column data is stripped from carriage returns, line feeds and commas to preserve structure.
     33=== Tab-delimited ===
     34Like above, but uses tabs (\t) instead of comma.
     36=== RSS - XML Content Syndication ===
     37All 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.
     40== Creating Custom Reports ==
     42''Creating a custom report requires a comfortable knowledge of SQL.''
     44A report is basically a single named SQL query, executed and presented by
     45Trac.  Reports can be viewed and created from a custom SQL expression directly
     46in from the web interface.
     48Typically, a report consists of a SELECT-expression from the 'ticket' table,
     49using the available columns and sorting the way you want it.
     51== Ticket columns ==
     52The ''ticket'' table has the following columns:
     53 * id
     54 * time
     55 * changetime
     56 * component
     57 * severity 
     58 * priority
     59 * owner
     60 * reporter
     61 * cc
     62 * url
     63 * version
     64 * milestone
     65 * status
     66 * resolution
     67 * summary
     68 * description
     70See TracTickets for a detailed description of the column fields.
     72'''all active tickets, sorted by priority and time'''
     74'''Example:''' ''All active tickets, sorted by priority and time''
     76SELECT id AS ticket, status, severity, priority, owner,
     77       time as created, summary FROM ticket
     78  WHERE status IN ('new', 'assigned', 'reopened')
     79  ORDER BY priority, time
     86== Advanced Reports: Dynamic Variables ==
     87For more flexible reports, Trac supports the use of ''dynamic variables'' in report SQL statements.
     88In short, dynamic variables are ''special'' strings that are replaced by custom data before query execution.
     90=== Using Variables in a Query ===
     91The syntax for dynamic variables is simple, any upper case word beginning with '$' is considered a variable.
     95SELECT id AS ticket,summary FROM ticket WHERE priority='$PRIORITY'
     98To assign a value to $PRIORITY when viewing the report, you must define it as an argument in the report URL, leaving out the the leading '$'.
     106=== Special/Constant Variables ===
     107There is one ''magic'' dynamic variable to allow practical reports, its value automatically set without having to change the URL.
     109 * $USER -- Username of logged in user.
     111Example (''List all tickets assigned to me''):
     113SELECT id AS ticket,summary FROM ticket WHERE owner='$USER'
     120== Advanced Reports: Custom Formatting ==
     121Trac is also capable of more advanced reports, including custom layouts,
     122result grouping and user-defined CSS styles. To create such reports, we'll use
     123specialized SQL statements to control the output of the Trac report engine.
     125== Special Columns ==
     126To format reports, TracReports looks for 'magic' column names in the query
     127result. These 'magic' names are processed and affect the layout and style of the
     128final report.
     130=== Automatically formatted columns ===
     131 * '''ticket''' -- Ticket ID number. Becomes a hyperlink to that ticket.
     132 * '''created, modified, date, time''' -- Format cell as a date and/or time.
     134 * '''description''' -- Ticket description field, parsed through the wiki engine.
     138SELECT id as ticket, created, status, summary FROM ticket
     141=== Custom formatting columns ===
     142Columns whose names begin and end with 2 underscores (Example: '''_''''''_color_''''''_''') are
     143assumed to be ''formatting hints'', affecting the appearance of the 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.
     149'''Example:''' ''List active tickets, grouped by milestone, colored by priority''
     151SELECT p.value AS __color__,
     152     t.milestone AS __group__,
     153     (CASE owner WHEN 'daniel' THEN 'font-weight: bold; background: red;' ELSE '' END) AS __style__,
     154 AS ticket, summary
     155  FROM ticket t,enum p
     156  WHERE t.status IN ('new', 'assigned', 'reopened')
     157    AND AND p.type='priority'
     158  ORDER BY t.milestone, p.value, t.severity, t.time
     161'''Note:''' A table join is used to match ''ticket'' priorities with their
     162numeric representation from the ''enum'' table.
     164=== Changing layout of report rows ===
     165By default, all columns on each row are display on a single row in the HTML
     166report, possibly formatted according to the descriptions above. However, it's
     167also possible to create multi-line report entries.
     169 * '''column_''' -- ''Break row after this''. By appending an underscore ('_') to the column name, the remaining columns will be be continued on a second line.
     171 * '''_column_''' -- ''Full row''. By adding an underscore ('_') both at the beginning and the end of a column name, the data will be shown on a separate row.
     173 * '''_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).
     175'''Example:''' ''List active tickets, grouped by milestone, colored by priority, with  description and multi-line layout''
     178SELECT p.value AS __color__,
     179       t.milestone AS __group__,
     180       (CASE owner
     181          WHEN 'daniel' THEN 'font-weight: bold; background: red;'
     182          ELSE '' END) AS __style__,
     183 AS ticket, summary AS summary_,             -- ## Break line here
     184       component,version, severity, milestone, status, owner,
     185       time AS created, changetime AS modified,         -- ## Dates are formatted
     186       description AS _description_,                    -- ## Uses a full row
     187       changetime AS _changetime, reporter AS _reporter -- ## Hidden from HTML output
     188  FROM ticket t,enum p
     189  WHERE t.status IN ('new', 'assigned', 'reopened')
     190    AND AND p.type='priority'
     191  ORDER BY t.milestone, p.value, t.severity, t.time
     196See also: TracTickets, TracQuery, TracGuide