Changes between Version 6 and Version 7 of TracIniReportCustomFieldSample

Timestamp:

Feb 24, 2007, 2:29:50 AM (17 years ago)

Author:

pombredanne@…

Comment:

Fixed some typos, non-english short texts, and reversed engineered some missin trac.ini snippets to make the examples easier to use, and added a new example

TracIniReportCustomFieldSample

@@ -1 @@
-= Report with CustomFields =
+= Report with TracTicketsCustomFields =
 
 Here are some examples of how to generate simple custom reports from TracTicketsCustomFields.
@@ -9 +9 @@
 Enjoy!
 
-Trac.ini
+'''Trac.ini:'''
 {{{
 
@@ -18 +18 @@
 }}}
 
-Custom SQL
+'''Custom SQL:'''
 {{{
 SELECT 
-   milestone as Proyectos,
-   sum(p.value) as Tiempo_Invertido
+   milestone as Project,
+   sum(p.value) as Inverted_Time
    FROM ticket t, ticket_custom p
    WHERE p.ticket = t.id and p.name = 'test_one'
@@ -30 +30 @@
 }}}
 
-BTW.Sorry my English and short text.
-
 
 == Example 2 ==
 
-Here's another longer example ... I have four fields in my ticket_custom, and I want them all to be seen in the report. If the existing field was a NULL, the report code adds the word "None" to the output, so I'm getting rid of that with a CASE statement. The main magic is the series of LEFT OUTER JOINs, which let me access each field of ticket_custom in turn.
+Here's another longer example ... I have four fields in my ticket-custom, and I want them all to be seen in the report. If the existing field was a NULL, the report code adds the word "None" to the output, so I'm getting rid of that with a CASE statement. The main magic is the series of LEFT OUTER JOINs, which let me access each custom field in turn.
 
+'''Trac.ini:'''
+{{{
+
+[ticket-custom]
+charge = text
+charge.label = Charge
+
+noncharge = text
+noncharge.label = Non charge
+
+sitevisit = text
+sitevisit.label = Site visit
+
+oohours = text
+oohours.label = Hours
+}}}
+
+
+'''Custom SQL:'''
 {{{
 SELECT DISTINCT 
@@ -74 +91 @@
 I added a custom ticket field to provide an idea of the percentage of the ticket completed so far.  This is a simple dropdown list where the developer can log their progress to the nearest 20%.
 
-So in my trac.ini I added:
-
+'''trac.ini:'''
 {{{
 [ticket-custom]
@@ -85 +101 @@
 
 Then to generate a simple report containing the new field, based on the default 'Active Tickets' report, I ended up with this:
+
+'''Custom SQL:'''
 
 {{{
@@ -103 +121 @@
  * the OUTER JOIN is the key to getting this to work
  * I'm not totally fluent in SQL, so this may not be the simplest way, but it works for me
+
+== Example 4 ==
+I have added a few custom fields to track roughly the amount of work spent on each ticket. One field is the estimated work (in days) and the iother is the actual work (in days). I needed a simple report to summarize the total amount of work for each milestone: estimated and actual. 
+
+'''trac.ini:'''
+{{{
+[ticket-custom]
+estimate = text
+estimate.label = Estimate
+
+actual = text
+actual.label = Actual
+}}}
+
+'''Custom SQL:'''
+
+{{{
+SELECT 
+   milestone AS Iteration,
+   SUM(estimate.value) AS Estimate,
+   SUM(actual.value) AS Actual
+
+  FROM ticket t
+
+  LEFT OUTER JOIN ticket_custom estimate ON
+       (t.id=estimate.ticket AND estimate.name='estimate')
+
+  LEFT OUTER JOIN ticket_custom actual ON
+       (t.id=actual.ticket AND actual.name='actual')
+
+  GROUP BY milestone 
+
+}}}