Cyberduck Mountain Duck CLI

Changes between Version 2 and Version 3 of TracReports


Ignore:
Timestamp:
Oct 8, 2006 12:11:46 PM (15 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracReports

    v2 v3  
    111111}}}
    112112
    113 To use multiple variables, separate them with an '&'.
     113To use multiple variables, separate them with an '&'.
    114114
    115115Example:
    116116{{{
    117  http://projects.edgewall.com/trac/reports/14?PRIORITY=high&SEVERITY=critical
     117 http://projects.edgewall.com/trac/reports/14?PRIORITY=high&SEVERITY=critical
    118118}}}
    119119
     
    211211If you have added custom fields to your tickets (experimental feature in 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.
    212212
    213 If 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 TracIniReportCustomFieldSample for some examples.
    214 
    215 ----
    216 See also: TracTickets, TracQuery, TracGuide
     213If 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 TracIniReportCustomFieldSample for some examples.
     214
     215----
     216See also: TracTickets, TracQuery, TracGuide185386303249