Changes between Version 1 and Version 2 of TracReports


Ignore:
Timestamp:
Apr 30, 2019 4:37:54 PM (6 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracReports

    v1 v2  
    1 = Trac Reports =
     1= Trac Reports
     2
    23[[TracGuideToc]]
    34
    4 The Trac reports module provides a simple, yet powerful reporting facility
    5 to present information about tickets in the Trac database.
    6 
    7 Rather than have its own report definition format, TracReports relies on standard SQL
    8 `SELECT` statements for custom report definition.
    9 
    10   '''Note:''' ''The report module is being phased out in its current form because it seriously limits the ability of the Trac team to make adjustments to the underlying database schema. We believe that the [wiki:TracQuery query module] is a good replacement that provides more flexibility and better usability. While there are certain reports that cannot yet be handled by the query module, we intend to further enhance it so that at some point the reports module can be completely removed. This also means that there will be no major enhancements to the report module anymore.''
    11 
    12   ''You can already completely replace the reports module by the query module simply by disabling the former in [wiki:TracIni trac.ini]:''
    13   {{{
     5The Trac reports module provides a simple, yet powerful reporting facility to present information about tickets in the Trac database.
     6
     7Rather than have its own report definition format, TracReports relies on standard SQL `SELECT` statements for custom report definition.
     8
     9  '''Note:''' The report module is being phased out in its current form because it seriously limits the ability of the Trac team to make adjustments to the underlying database schema. We believe that the [wiki:TracQuery query module] is a good replacement that provides more flexibility and better usability. While there are certain reports that cannot yet be handled by the query module, we intend to further enhance it so that at some point the reports module can be completely removed. This also means that there will be no major enhancements to the report module anymore.
     10
     11  You can already completely replace the reports module by the query module simply by disabling the former in [wiki:TracIni trac.ini]:
     12  {{{#!ini
    1413  [components]
    1514  trac.ticket.report.* = disabled
    1615  }}}
    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 
     16  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.
    1917
    2018A report consists of these basic parts:
    … …  
    2523 * '''Footer''' — Links to alternative download formats for this report.
    2624
    27 == Changing Sort Order ==
     25== Changing Sort Order
     26
    2827Simple reports - ungrouped reports to be specific - can be changed to be sorted by any column simply by clicking the column header.
    2928
    3029If a column header is a hyperlink (red), click the column you would like to sort by. Clicking the same header again reverses the order.
    3130
    32 == Changing Report Numbering ==
    33 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)'':
     31== Changing Report Numbering
     32
     33There 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:
    3434 * id integer PRIMARY KEY
    3535 * author text
    … …  
    3838 * description text
    3939Changing the ID changes the shown order and number in the ''Available Reports'' list and the report's perma-link. This is done by running something like:
    40 {{{
    41 update report set id=5 where id=3;
    42 }}}
    43 Keep in mind that the integrity has to be maintained (i.e., ID has to be unique, and you don't want to exceed the max, since that's managed by SQLite someplace).
     40{{{#!sql
     41UPDATE report SET id = 5 WHERE id = 3;
     42}}}
     43Keep in mind that the integrity has to be maintained, ie ID has to be unique, and you don't want to exceed the max, since that's managed by SQLite someplace.
    4444
    4545You may also need to update or remove the report number stored in the report or query.
    4646
    47 == Navigating Tickets ==
     47== Navigating Tickets
     48
    4849Clicking 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.
    4950
    50 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)''
    51 
    52 == Alternative Download Formats ==
     51You 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).
     52
     53== Alternative Download Formats
     54
    5355Aside from the default HTML view, reports can also be exported in a number of alternative formats.
    5456At the bottom of the report page, you will find a list of available data formats. Click the desired link to
    5557download the alternative report format.
    5658
    57 === Comma-delimited - CSV (Comma Separated Values) ===
     59=== Comma-delimited - CSV (Comma Separated Values)
     60
    5861Export the report as plain text, each row on its own line, columns separated by a single comma (',').
    5962'''Note:''' The output is fully escaped so carriage returns, line feeds, and commas will be preserved in the output.
    6063
    61 === Tab-delimited ===
     64=== Tab-delimited
     65
    6266Like above, but uses tabs (\t) instead of comma.
    6367
    64 === RSS - XML Content Syndication ===
     68=== RSS - XML Content Syndication
     69
    6570All reports support syndication using XML/RSS 2.0. To subscribe to an RSS feed, click the orange 'XML' icon at the bottom of the page. See TracRss for general information on RSS support in Trac.
    6671
    67 ----
    68 
    69 == Creating Custom Reports ==
    70 
    71 ''Creating a custom report requires a comfortable knowledge of SQL.''
    72 
    73 A report is basically a single named SQL query, executed and presented by
    74 Trac.  Reports can be viewed and created from a custom SQL expression directly
    75 in the web interface.
    76 
    77 Typically, a report consists of a SELECT-expression from the 'ticket' table,
    78 using the available columns and sorting the way you want it.
    79 
    80 == Ticket columns ==
     72== Creating Custom Reports
     73
     74Creating a custom report requires a comfortable knowledge of SQL.
     75
     76Note that you need to set up [TracPermissions#Reports permissions] in order to see the buttons for adding or editing reports.
     77
     78A report is basically a single named SQL query, executed and presented by Trac. Reports can be viewed and created from a custom SQL expression directly in the web interface.
     79
     80Typically, a report consists of a SELECT-expression from the 'ticket' table, using the available columns and sorting the way you want it.
     81
     82== Ticket columns
     83
    8184The ''ticket'' table has the following columns:
    8285 * id
    … …  
    101104
    102105Example: '''All active tickets, sorted by priority and time'''
    103 {{{
    104 SELECT id AS ticket, status, severity, priority, owner,
    105        time AS created, summary FROM ticket
    106   WHERE status IN ('new', 'assigned', 'reopened')
    107   ORDER BY priority, time
    108 }}}
    109 
    110 ---
    111 
    112 == Advanced Reports: Dynamic Variables ==
     106{{{#!sql
     107SELECT id AS ticket, status, severity, priority, owner, time AS created, summary
     108FROM ticket
     109WHERE status IN ('new', 'assigned', 'reopened')
     110ORDER BY priority, time
     111}}}
     112
     113== Advanced Reports: Dynamic Variables
     114
    113115For more flexible reports, Trac supports the use of ''dynamic variables'' in report SQL statements.
    114116In short, dynamic variables are ''special'' strings that are replaced by custom data before query execution.
    115117
    116 === Using Variables in a Query ===
     118=== Using Variables in a Query
     119
    117120The syntax for dynamic variables is simple, any upper case word beginning with '$' is considered a variable.
    118121
    119122Example:
    120 {{{
     123{{{#!sql
    121124SELECT id AS ticket,summary FROM ticket WHERE priority=$PRIORITY
    122125}}}
    123126
    124 To assign a value to $PRIORITY when viewing the report, you must define it as an argument in the report URL, leaving out the leading '$'.
    125 
    126 Example:
     127To assign a value to $PRIORITY when viewing the report, you must define it as an argument in the report URL, leaving out the leading '$':
    127128{{{
    128129 http://trac.edgewall.org/reports/14?PRIORITY=high
    129130}}}
    130131
    131 To use multiple variables, separate them with an '&'.
    132 
    133 Example:
     132To use multiple variables, separate them with an '&':
    134133{{{
    135134 http://trac.edgewall.org/reports/14?PRIORITY=high&SEVERITY=critical
    136135}}}
    137136
    138 
    139 === !Special/Constant Variables ===
     137=== !Special/Constant Variables
     138
    140139There is one dynamic variable whose value is set automatically (the URL does not have to be changed) to allow practical reports.
    141140
    142141 * $USER — Username of logged in user.
    143142
    144 Example (''List all tickets assigned to me''):
    145 {{{
     143Example: List all tickets assigned to me:
     144{{{#!sql
    146145SELECT id AS ticket,summary FROM ticket WHERE owner=$USER
    147146}}}
    148147
    149 
    150 ----
    151 
    152 
    153 == Advanced Reports: Custom Formatting ==
    154 Trac is also capable of more advanced reports, including custom layouts,
    155 result grouping and user-defined CSS styles. To create such reports, we'll use
    156 specialized SQL statements to control the output of the Trac report engine.
    157 
    158 == Special Columns ==
    159 To format reports, TracReports looks for 'magic' column names in the query
    160 result. These 'magic' names are processed and affect the layout and style of the
    161 final report.
    162 
    163 === Automatically formatted columns ===
     148== Advanced Reports: Custom Formatting
     149
     150Trac is also capable of more advanced reports, including custom layouts, result grouping and user-defined CSS styles. To create such reports, we will use specialized SQL statements to control the output of the Trac report engine.
     151
     152=== Special Columns
     153
     154To format reports, TracReports looks for 'magic' column names in the query result. These 'magic' names are processed and affect the layout and style of the final report.
     155
     156=== Automatically formatted columns
     157
    164158 * '''ticket''' — Ticket ID number. Becomes a hyperlink to that ticket.
    165159 * '''id''' — same as '''ticket''' above when '''realm''' is not set
    166160 * '''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)
     161   - 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
    167162 * '''created, modified, date, time''' — Format cell as a date and/or time.
    168163 * '''description''' — Ticket description field, parsed through the wiki engine.
    169164
    170165'''Example:'''
    171 {{{
     166{{{#!sql
    172167SELECT id AS ticket, created, status, summary FROM ticket
    173168}}}
    … …  
    177172See trac:wiki/CookBook/Configuration/Reports for some example of creating reports for realms other than ''ticket''.
    178173
    179 === Custom formatting columns ===
     174=== Custom formatting columns
     175
    180176Columns whose names begin and end with 2 underscores (Example: '''`__color__`''') are
    181177assumed to be ''formatting hints'', affecting the appearance of the row.
    … …  
    194190</div>
    195191}}}
    196  * '''`__style__`''' — A custom CSS style expression to use for the current row.
     192 * '''`__style__`''' — A custom CSS style expression to use on the `<tr>` element of the current row.
     193 * '''`__class__`''' — Zero or more space-separated CSS class names to be set on the `<tr>` element of the current row. These classes are added to the class name derived from `__color__` and the odd / even indicator.
    197194
    198195'''Example:''' ''List active tickets, grouped by milestone, group header linked to milestone page, colored by priority''
    199 {{{
     196{{{#!sql
    200197SELECT p.value AS __color__,
    201198     t.milestone AS __group__,
    202199     '../milestone/' || t.milestone AS __grouplink__,
    203200     (CASE owner WHEN 'daniel' THEN 'font-weight: bold; background: red;' ELSE '' END) AS __style__,
    204        t.id AS ticket, summary
    205   FROM ticket t,enum p
    206   WHERE t.status IN ('new', 'assigned', 'reopened')
    207     AND p.name=t.priority AND p.type='priority'
    208   ORDER BY t.milestone, p.value, t.severity, t.time
    209 }}}
    210 
    211 '''Note:''' A table join is used to match ''ticket'' priorities with their
    212 numeric representation from the ''enum'' table.
     201     t.id AS ticket, summary
     202FROM ticket t,enum p
     203WHERE t.status IN ('new', 'assigned', 'reopened')
     204  AND p.name = t.priority AND p.type = 'priority'
     205ORDER BY t.milestone, p.value, t.severity, t.time
     206}}}
     207
     208'''Note:''' A table join is used to match ''ticket'' priorities with their numeric representation from the ''enum'' table.
    213209
    214210=== Changing layout of report rows === #column-syntax
    215 By default, all columns on each row are display on a single row in the HTML
    216 report, possibly formatted according to the descriptions above. However, it's
    217 also possible to create multi-line report entries.
    218 
    219  * '''`column_`''' — ''Break row after this''. By appending an underscore ('_') to the column name, the remaining columns will be be continued on a second line.
     211
     212By default, all columns on each row are display on a single row in the HTML report, possibly formatted according to the descriptions above. However, it is also possible to create multi-line report entries.
     213
     214 * '''`column_`''' — ''Break row after this''. By appending an underscore ('_') to the column name, the remaining columns will be continued on a second line.
    220215
    221216 * '''`_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.
    … …  
    226221'''Example:''' ''List active tickets, grouped by milestone, colored by priority, with  description and multi-line layout''
    227222
    228 {{{
     223{{{#!sql
    229224SELECT p.value AS __color__,
    230225       t.milestone AS __group__,
    … …  
    237232       description AS _description_,                    -- ## Uses a full row
    238233       changetime AS _changetime, reporter AS _reporter -- ## Hidden from HTML output
    239   FROM ticket t,enum p
    240   WHERE t.status IN ('new', 'assigned', 'reopened')
    241     AND p.name=t.priority AND p.type='priority'
    242   ORDER BY t.milestone, p.value, t.severity, t.time
    243 }}}
    244 
    245 === Reporting on custom fields ===
    246 
    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.
     234FROM ticket t,enum p
     235WHERE t.status IN ('new', 'assigned', 'reopened')
     236  AND p.name = t.priority AND p.type = 'priority'
     237ORDER BY t.milestone, p.value, t.severity, t.time
     238}}}
     239
     240=== Reporting on custom fields
     241
     242If 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.
    248243
    249244If 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.
    250245
    251 '''Note that you need to set up permissions in order to see the buttons for adding or editing reports.'''
     246=== A note about SQL rewriting #rewriting
     247
     248Beyond the relatively trivial replacement of dynamic variables, the SQL query is also altered in order to support two features of the reports:
     249 1. [#sort-order changing the sort order]
     250 1. pagination support (limitation of the number of result rows displayed on each page)
     251In order to support the first feature, the sort column is inserted in the `ORDER BY` clause in the first position or in the second position if a `__group__` column is specified (an `ORDER BY` clause is created if needed). In order to support pagination, a `LIMIT ... OFFSET ...` clause is appended.
     252The query might be too complex for the automatic rewrite to work correctly, resulting in an erroneous query. In this case you still have the possibility to control exactly how the rewrite is done by manually inserting the following tokens:
     253 - `@SORT_COLUMN@`, the place where the name of the selected sort column will be inserted,
     254 - `@LIMIT_OFFSET@`, the place where the pagination support clause will be added
     255Note that if you write them after an SQL comment, `--`, you'll effectively disable rewriting if this is what you want!
     256
     257Let's take an example, consider the following SQL query:
     258{{{#!sql
     259-- ## 4: Assigned, Active Tickets by Owner ## --
     260
     261--
     262-- List assigned tickets, group by ticket owner, sorted by priority.
     263--
     264
     265SELECT p.value AS __color__,
     266   owner AS __group__,
     267   id AS ticket, summary, component, milestone, t.type AS type, severity, time AS created,
     268   changetime AS _changetime, description AS _description,
     269   reporter AS _reporter
     270FROM ticket t,enum p
     271WHERE status = 'assigned'
     272  AND p.name = t.priority AND p.type = 'priority'
     273ORDER BY __group__, p.value, severity, time
     274}}}
     275
     276The automatic rewrite will be the following (4 rows per page, page 2, sorted by `component`):
     277{{{#!sql
     278SELECT p.value AS __color__,
     279   owner AS __group__,
     280   id AS ticket, summary, component, milestone, t.type AS type, severity, time AS created,
     281   changetime AS _changetime, description AS _description,
     282   reporter AS _reporter
     283FROM ticket t,enum p
     284WHERE status = 'assigned'
     285  AND p.name = t.priority AND p.type = 'priority'
     286ORDER BY __group__ ASC, `component` ASC,  __group__, p.value, severity, time
     287LIMIT 4 OFFSET 4
     288}}}
     289
     290The equivalent SQL query with the rewrite tokens would have been:
     291{{{#!sql
     292SELECT p.value AS __color__,
     293   owner AS __group__,
     294   id AS ticket, summary, component, milestone, t.type AS type, severity, time AS created,
     295   changetime AS _changetime, description AS _description,
     296   reporter AS _reporter
     297FROM ticket t,enum p
     298WHERE status = 'assigned'
     299  AND p.name = t.priority AND p.type = 'priority'
     300ORDER BY __group__, @SORT_COLUMN@, p.value, severity, time
     301@LIMIT_OFFSET@
     302}}}
     303
     304If you want to always sort first by priority and only then by the user selected sort column, simply use the following `ORDER BY` clause:
     305{{{#!sql
     306ORDER BY __group__, p.value, @SORT_COLUMN@, severity, time
     307}}}
    252308
    253309----