Changes between Version 1 and Version 2 of TracTicketsCustomFields

Timestamp:

Apr 28, 2008, 2:20:40 PM (17 years ago)

Author:

trac

Comment:

--

TracTicketsCustomFields

@@ -17 +17 @@
    * label: Descriptive label.
    * value: Default value.
-   * order: Sort order placement. (Determines relative placement in forms.)
+   * order: Sort order placement. (Determines relative placement in forms with respect to other custom fields.)
  * '''checkbox''': A boolean value check box.
    * label: Descriptive label.
@@ -23 +23 @@
    * order: Sort order placement.
  * '''select''': Drop-down select box. Uses a list of values.
+   * label: Descriptive label.
    * options: List of values, separated by '''|''' (vertical pipe).
-   * value: Default value (Item #, starting at 0).
+   * value: Default value (one of the values from options).
    * order: Sort order placement.
  * '''radio''': Radio buttons. Essentially the same as '''select'''.
@@ -56 +57 @@
 test_four.label = My selectbox
 test_four.options = one|two|third option|four
-test_four.value = 2
+test_four.value = two
 
 test_five = radio
@@ -70 +71 @@
 }}}
 
-''Note: To make an entering an option for a `select` type field optional, specify a leading `|` in the `fieldname.options` option.''
+''Note: To make entering an option for a `select` type field optional, specify a leading `|` in the `fieldname.options` option.''
 
 === 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 `ticket_custom` 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, ticket_custom 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 that field defined, and thus they will never show up on this ticket query. If you go back and modify those tickets, the field will be defined, and they will appear in the query. If that's all you want, you're set.
+
+However, if you want to show all ticket entries (with progress defined and without), you need to use a `JOIN` for every custom field that is in the query.
 {{{
 #!sql