Changes between Version 1 and Version 2 of TracTicketsCustomFields

Author:

trac (IP: 127.0.0.1)

Timestamp:

06/18/06 19:44:20 (1 year ago)

Comment:

--

TracTicketsCustomFields

@@ -1 +1 @@
-= Custom Ticket Fields =
- adding custom, user-defined, fields to the ticket module. Using custom fields, you can add typed, site-specific,
+s adding custom, user-defined fields to the ticket module. Using custom fields, you can add typed, site-specific
-
-
-
-
-
-
-
+
+
-
-The syntax of each field definition is:
- ...
-}}}
-Looking at the example below should help
+The example below should help to
-
-=== Available Field Types and Options ===
-   * label: Descriptive label.
-   * value: Default text.
-width
-height
+cols
+rows
-   * order: Sort order placement.
-
-{{{
-[ticket-custom]
+
-test_one = text
-test_one.label = Just a text box
-test_six.label = This is a large textarea
-test_six.value = Default text
-width
-height
+cols
+rows
-}}}
+
+''Note: To make an 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.
+
+The following example includes a custom ticket field named `progress` in the report:
+{{{
+#!sql
+SELECT p.value AS __color__,
+   id AS ticket, summary, component, version, milestone, severity,
+   (CASE status WHEN 'assigned' THEN owner||' *' ELSE owner END) AS owner,
+   time AS created,
+   changetime AS _changetime, description AS _description,
+   reporter AS _reporter,
+  (CASE WHEN c.value = '0' THEN 'None' ELSE c.value END) AS progress
+  FROM ticket t
+     LEFT OUTER JOIN ticket_custom c ON (t.id = c.ticket AND c.name = 'progress')
+     JOIN enum p ON p.name = t.priority AND p.type='priority'
+  WHERE status IN ('new', 'assigned', 'reopened')
+  ORDER BY p.value, milestone, severity, time
+}}}
+
+Note in particular the `LEFT OUTER JOIN` statement here.
-
-----