Changes between Version 1 and Version 2 of TracReports

Show
Ignore:
Timestamp:
04/01/08 05:51:22 (14 years ago)
Author:
trac (IP: 127.0.0.1)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracReports

    v1 v2  
    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.''''' 
     20 
    1921A report consists of these basic parts: 
    2022 * '''ID''' -- Unique (sequential) identifier  
     
    2931If a column header is a hyperlink (red), click the column you would like to sort by. Clicking the same header again reverses the order. 
    3032 
     33== Navigating Tickets == 
     34Clicking 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. 
     35 
     36You 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)'' 
    3137 
    3238== Alternative Download Formats == 
     
    6167The ''ticket'' table has the following columns: 
    6268 * id 
     69 * type 
    6370 * time 
    6471 * changetime 
     
    7582 * summary 
    7683 * description 
     84 * keywords 
    7785 
    7886See TracTickets for a detailed description of the column fields. 
     
    101109Example: 
    102110{{{ 
    103 SELECT id AS ticket,summary FROM ticket WHERE priority='$PRIORITY' 
    104 }}} 
    105  
    106 To assign a value to $PRIORITY when viewing the report, you must define it as an argument in the report URL, leaving out the the leading '$'. 
     111SELECT id AS ticket,summary FROM ticket WHERE priority=$PRIORITY 
     112}}} 
     113 
     114To assign a value to $PRIORITY when viewing the report, you must define it as an argument in the report URL, leaving out the leading '$'. 
    107115 
    108116Example: 
    109117{{{ 
    110  http://projects.edgewall.com/trac/reports/14?PRIORITY=high 
     118 http://trac.edgewall.org/reports/14?PRIORITY=high 
    111119}}} 
    112120 
     
    115123Example: 
    116124{{{ 
    117  http://projects.edgewall.com/trac/reports/14?PRIORITY=high&SEVERITY=critical 
     125 http://trac.edgewall.org/reports/14?PRIORITY=high&SEVERITY=critical 
    118126}}} 
    119127 
     
    126134Example (''List all tickets assigned to me''): 
    127135{{{ 
    128 SELECT id AS ticket,summary FROM ticket WHERE owner='$USER' 
     136SELECT id AS ticket,summary FROM ticket WHERE owner=$USER 
    129137}}} 
    130138 
     
    160168 * '''`__group__`''' -- Group results based on values in this column. Each group will have its own header and table. 
    161169 * '''`__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. 
     170{{{ 
     171#!html 
     172<div style="margin-left:7.5em">Defaults:  
     173<span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #fdc; border-color: #e88; color: #a22">Color 1</span> 
     174<span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #ffb; border-color: #eea; color: #880">Color 2</span> 
     175<span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #fbfbfb; border-color: #ddd; color: #444">Color 3</span> 
     176<span style="border: none; color: #333; background: transparent; font-size: 85%; background: #e7ffff; border-color: #cee; color: #099">Color 4</span> 
     177<span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #e7eeff; border-color: #cde; color: #469">Color 5</span> 
     178</div> 
     179}}} 
    162180 * '''`__style__`''' -- A custom CSS style expression to use for the current row.  
    163181 
     
    209227=== Reporting on custom fields === 
    210228 
    211 If 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. 
     229If 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. 
    212230 
    213231If 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. 
    214232 
    215 ---- 
    216 See also: TracTickets, TracQuery, TracGuide 
     233'''Note that you need to set up permissions in order to see the buttons for adding or editing reports.''' 
     234 
     235---- 
     236See also: TracTickets, TracQuery, TracGuide, [http://www.sqlite.org/lang_expr.html Query Language Understood by SQLite] 
Home
About PCA
Reference Data Services (RDS)
RDS Operations Support
Meetings and Conferences
ISO 15926
Special Interest Groups
Technical Advisory Board
Norwegian Continental Shelf Std
Projects
Search