Edgewall Software

Changes between Version 45 and Version 46 of TracReports


Ignore:
Timestamp:
Apr 23, 2010, 10:45:58 AM (14 years ago)
Author:
Mikael Relbe
Comment:

Use unicode emdash

Legend:

Unmodified
Added
Removed
Modified
  • TracReports

    v45 v46  
    2020
    2121A report consists of these basic parts:
    22  * '''ID''' -- Unique (sequential) identifier
    23  * '''Title'''  -- Descriptive title
    24  * '''Description'''  -- A brief description of the report, in WikiFormatting text.
    25  * '''Report Body''' -- List of results from report query, formatted according to the methods described below.
    26  * '''Footer''' -- Links to alternative download formats for this report.
     22 * '''ID''' Unique (sequential) identifier
     23 * '''Title''' Descriptive title
     24 * '''Description''' A brief description of the report, in WikiFormatting text.
     25 * '''Report Body''' List of results from report query, formatted according to the methods described below.
     26 * '''Footer''' Links to alternative download formats for this report.
    2727
    2828== Changing Sort Order ==
     
    141141There is one dynamic variable whose value is set automatically (the URL does not have to be changed) to allow practical reports.
    142142
    143  * $USER -- Username of logged in user.
     143 * $USER Username of logged in user.
    144144
    145145Example (''List all tickets assigned to me''):
     
    163163
    164164=== Automatically formatted columns ===
    165  * '''ticket''' -- Ticket ID number. Becomes a hyperlink to that ticket.
    166  * '''id''' -- same as '''ticket''' above when '''realm''' is not set
    167  * '''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)
    168  * '''created, modified, date, time''' -- Format cell as a date and/or time.
    169  * '''description''' -- Ticket description field, parsed through the wiki engine.
     165 * '''ticket''' Ticket ID number. Becomes a hyperlink to that ticket.
     166 * '''id''' same as '''ticket''' above when '''realm''' is not set
     167 * '''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)
     168 * '''created, modified, date, time''' Format cell as a date and/or time.
     169 * '''description''' Ticket description field, parsed through the wiki engine.
    170170
    171171'''Example:'''
     
    182182assumed to be ''formatting hints'', affecting the appearance of the row.
    183183 
    184  * '''`__group__`''' -- Group results based on values in this column. Each group will have its own header and table.
    185  * '''`__grouplink__`''' -- Make the header of each group a link to the specified URL. The URL is taken from the first row of each group.
    186  * '''`__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.
     184 * '''`__group__`''' Group results based on values in this column. Each group will have its own header and table.
     185 * '''`__grouplink__`''' Make the header of each group a link to the specified URL. The URL is taken from the first row of each group.
     186 * '''`__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.
    187187{{{
    188188#!html
     
    195195</div>
    196196}}}
    197  * '''`__style__`''' -- A custom CSS style expression to use for the current row.
     197 * '''`__style__`''' A custom CSS style expression to use for the current row.
    198198
    199199'''Example:''' ''List active tickets, grouped by milestone, group header linked to milestone page, colored by priority''
     
    218218also possible to create multi-line report entries.
    219219
    220  * '''`column_`''' -- ''Break row after this''. By appending an underscore ('_') to the column name, the remaining columns will be be continued on a second line.
    221 
    222  * '''`_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.
    223 
    224  * '''`_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).
     220 * '''`column_`''' ''Break row after this''. By appending an underscore ('_') to the column name, the remaining columns will be be continued on a second line.
     221
     222 * '''`_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.
     223
     224 * '''`_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).
    225225   This can be used to hide any kind of column, even important ones required for identifying the resource, e.g. `id as _id` will hide the '''Id''' column but the link to the ticket will be present.
    226226