Changes between Version 15 and Version 16 of TracTicketsCustomFields

Timestamp:

Oct 1, 2006, 11:34:47 PM (18 years ago)

Author:

sid@…

Comment:

Add more detail to using custom fields in reports

TracTicketsCustomFields

@@ -75 +75 @@
 === Reports Involving Custom Fields ===
 
-The SQL required for TracReports to include custom ticket fields is relatively hard to get right. You need a `JOIN` with the `ticket_custom` field for every custom field that should be involved.
+Custom ticket fields are stored in the `custom_ticket` table, not in the `ticket` table. So to display the values from custom fields in a report, you will need a join on the 2 tables. Let's use an example with a custom ticket field called `progress`.
 
-The following example includes a custom ticket field named `progress` in the report:
+{{{
+#!sql
+SELECT p.value AS __color__,
+   id AS ticket, summary, owner, c.value AS progress
+  FROM ticket t, enum p, custom_ticket c
+  WHERE status IN ('assigned') AND t.id = c.ticket AND c.name = 'progress'
+AND p.name = t.priority AND p.type = 'priority'
+  ORDER BY p.value
+}}}
+'''Note''' that this will only show tickets that have progress set in them, which is '''not the same as showing all tickets'''. If you created this custom ticket field ''after'' you have already created some tickets, they will not have this custom field defined for that ticket, and thus will never show up on this ticket query. If that's all you want, you're set. 
+
+If you want to show all ticket entries (with progress and without), you need to use a `JOIN` for every custom field that is in the query.
 {{{
 #!sql