Changes between Version 2 and Version 3 of TracReports


Ignore:
Timestamp:
11/18/04 18:02:59 (15 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracReports

    v2 v3  
    11= Trac Reports =
     2[[TracGuideToc]]
     3
    24The Trac reports module provides a simple, yet powerful reporting facility
    3 for presenting information about tickets from the Trac database.
     5to present information about tickets in the Trac database.
    46
    5 Rather than have its own report format, TracReports relies on standard SQL
     7Rather than have its own report definition format, TracReports relies on standard SQL
    68SELECT statements for custom report definition.
    79
     
    1214 * Report Body -- List of results from report query, formatted according to the methods described below.
    1315 * Footer -- Links to alternative download formats for this report.
     16
     17
     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.
     20
     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.
    1422
    1523
     
    2937All 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.
    3038
    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 
    3639----
    3740== Creating Custom Reports ==
    3841
    39 Creating a custom report requires knowing and using the SQL query language.
     42''Creating a custom report requires a comfortable knowledge of SQL.''
    4043
    4144A report is basically a single named SQL query, executed and presented by
     
    128131 * '''ticket''' -- Ticket ID number. Becomes a hyperlink to that ticket.
    129132 * '''created, modified, date, time''' -- Format cell as a date and/or time.
     133
    130134 * '''description''' -- Ticket description field, parsed through the wiki engine.
    131135
     
    136140
    137141=== Custom formatting columns ===
    138 Columns whose name begins and ends with '__' (Example: '''__color__''') are
     142Columns whose names begin and end with 2 underscores (Example: '''_''''''_color_''''''_''') are
    139143assumed to be ''formatting hints'', affecting the appearance of the row.
    140144 
    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.
    144148
    145149'''Example:''' ''List active tickets, grouped by milestone, colored by priority''
     
    190194
    191195----
    192 See also: TracTickets, TracGuide
     196See also: TracTickets, TracQuery, TracGuide