Changes between Version 3 and Version 4 of TracReports


Ignore:
Timestamp:
2008-07-22T15:10:25Z (7 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracReports

    v3 v4  
    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== Changing Report Numbering ==
     34There 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 (as of 0.10):
     35 * id integer PRIMARY KEY
     36 * author text
     37 * title text
     38 * query text
     39 * description text
     40Changing 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:
     41{{{
     42update report set id=5 where id=3;
     43}}}
     44Keep 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).
     45
     46== Navigating Tickets ==
     47Clicking 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.
     48
     49You 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)''
    3150
    3251== Alternative Download Formats ==
     
    6180The ''ticket'' table has the following columns:
    6281 * id
     82 * type
    6383 * time
    6484 * changetime
     
    7595 * summary
    7696 * description
     97 * keywords
    7798
    7899See TracTickets for a detailed description of the column fields.
     
    101122Example:
    102123{{{
    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 '$'.
     124SELECT id AS ticket,summary FROM ticket WHERE priority=$PRIORITY
     125}}}
     126
     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 '$'.
    107128
    108129Example:
    109130{{{
    110  http://projects.edgewall.com/trac/reports/14?PRIORITY=high
     131 http://trac.edgewall.org/reports/14?PRIORITY=high
    111132}}}
    112133
     
    115136Example:
    116137{{{
    117  http://projects.edgewall.com/trac/reports/14?PRIORITY=high&SEVERITY=critical
     138 http://trac.edgewall.org/reports/14?PRIORITY=high&SEVERITY=critical
    118139}}}
    119140
     
    126147Example (''List all tickets assigned to me''):
    127148{{{
    128 SELECT id AS ticket,summary FROM ticket WHERE owner='$USER'
     149SELECT id AS ticket,summary FROM ticket WHERE owner=$USER
    129150}}}
    130151
     
    160181 * '''`__group__`''' -- Group results based on values in this column. Each group will have its own header and table.
    161182 * '''`__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.
     183{{{
     184#!html
     185<div style="margin-left:7.5em">Defaults:
     186<span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #fdc; border-color: #e88; color: #a22">Color 1</span>
     187<span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #ffb; border-color: #eea; color: #880">Color 2</span>
     188<span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #fbfbfb; border-color: #ddd; color: #444">Color 3</span>
     189<span style="border: none; color: #333; background: transparent; font-size: 85%; background: #e7ffff; border-color: #cee; color: #099">Color 4</span>
     190<span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #e7eeff; border-color: #cde; color: #469">Color 5</span>
     191</div>
     192}}}
    162193 * '''`__style__`''' -- A custom CSS style expression to use for the current row.
    163194
     
    209240=== Reporting on custom fields ===
    210241
    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.
     242If 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.
    212243
    213244If 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.
    214245
    215 ----
    216 See also: TracTickets, TracQuery, TracGuide
     246'''Note that you need to set up permissions in order to see the buttons for adding or editing reports.'''
     247
     248----
     249See also: TracTickets, TracQuery, TracGuide, [http://www.sqlite.org/lang_expr.html Query Language Understood by SQLite]