Changes between Version 2 and Version 3 of TracReports


Ignore:
Timestamp:
Jun 8, 2011, 7:44:12 PM (13 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracReports

    v2 v3  
    1717  ''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.''
    1818
    19   '''''You will almost definitely need to restart your httpd at this point.'''''
    2019
    2120A report consists of these basic parts:
     
    4342}}}
    4443Keep 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).
     44
     45You may also need to update or remove the report number stored in the report or query.
    4546
    4647== Navigating Tickets ==
     
    104105{{{
    105106SELECT id AS ticket, status, severity, priority, owner,
    106        time as created, summary FROM ticket
     107       time AS created, summary FROM ticket
    107108  WHERE status IN ('new', 'assigned', 'reopened')
    108109  ORDER BY priority, time
     
    166167=== Automatically formatted columns ===
    167168 * '''ticket''' -- Ticket ID number. Becomes a hyperlink to that ticket.
     169 * '''id''' -- same as '''ticket''' above when '''realm''' is not set
     170 * '''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)
    168171 * '''created, modified, date, time''' -- Format cell as a date and/or time.
    169 
    170172 * '''description''' -- Ticket description field, parsed through the wiki engine.
    171173
    172174'''Example:'''
    173175{{{
    174 SELECT id as ticket, created, status, summary FROM ticket
    175 }}}
     176SELECT id AS ticket, created, status, summary FROM ticket
     177}}}
     178
     179Those columns can also be defined but marked as hidden, see [#column-syntax below].
    176180
    177181=== Custom formatting columns ===
     
    208212numeric representation from the ''enum'' table.
    209213
    210 === Changing layout of report rows ===
     214=== Changing layout of report rows === #column-syntax
    211215By default, all columns on each row are display on a single row in the HTML
    212216report, possibly formatted according to the descriptions above. However, it's
     
    218222
    219223 * '''`_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).
     224   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.
    220225
    221226'''Example:''' ''List active tickets, grouped by milestone, colored by priority, with  description and multi-line layout''