Changes between Version 1 and Version 2 of TracReports

Timestamp:

Sep 16, 2005, 12:03:53 AM (19 years ago)

Author:

trac

Comment:

--

TracReports

@@ -29 +29 @@
 === Comma-delimited - CSV (Comma Separated Values) ===
 Export the report as plain text, each row on its own line, columns separated by a single comma (',').
-'''Note:''' Column data is stripped from carriage returns, line feeds and commas to preserve structure.
+'''Note:''' Carriage returns, line feeds, and commas are stripped from column data to preserve the CSV structure.
 
 === Tab-delimited ===
@@ -35 +35 @@
 
 === RSS - XML Content Syndication ===
-All reports support syndication using XML/RSS 2.0. To subscribe to a , click the the orange 'XML' icon at the bottom of the page. See TracRss for general information on RSS support in Trac.
+All reports support syndication using XML/RSS 2.0. To subscribe to an RSS feed, click the orange 'XML' icon at the bottom of the page. See TracRss for general information on RSS support in Trac.
 
 ----
@@ -103 +103 @@
 }}}
 
+To use multiple variables, separate them with an '&'.
+
+Example:
+{{{
+ http://projects.edgewall.com/trac/reports/14?PRIORITY=high&SEVERITY=critical
+}}}
+
 
 === Special/Constant Variables ===
@@ -192 +199 @@
 }}}
 
+=== Reporting on custom fields ===
+
+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.
+
+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.
 
 ----