Changes between Version 1 and Version 2 of TracTicketsCustomFields

Timestamp:

Feb 24, 2012, 11:56:25 AM (13 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.)
+   * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting. (''since 0.11.3'')
  * '''checkbox''': A boolean value check box.
    * label: Descriptive label.
@@ -25 +26 @@
    * 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'''.
    * 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.
  * '''textarea''': Multi-line text area.
@@ -38 +39 @@
    * rows: Height in lines.
    * order: Sort order placement.
+   * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting. (''since 0.11.3'')
 
 === Sample Config ===
@@ -48 +50 @@
 test_two = text
 test_two.label = Another text-box
-test_two.value = Just a default value
+test_two.value = Default [mailto:joe@nospam.com owner]
+test_two.format = wiki
 
 test_three = checkbox
@@ -57 +60 @@
 test_four.label = My selectbox
 test_four.options = one|two|third option|four
-test_four.value = 2
+test_four.value = two
 
 test_five = radio
 test_five.label = Radio buttons are fun
 test_five.options = uno|dos|tres|cuatro|cinco
-test_five.value = 1
+test_five.value = dos
 
 test_six = textarea
@@ -75 +78 @@
 === 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
@@ -96 +110 @@
 Note in particular the `LEFT OUTER JOIN` statement here.
 
+=== Updating the database ===
+
+As noted above, any tickets created before a custom field has been defined will not have a value for that field. Here's a bit of SQL (tested with SQLite) that you can run directly on the Trac database to set an initial value for custom ticket fields. Inserts the default value of 'None' into a custom field called 'request_source' for all tickets that have no existing value:
+
+{{{
+#!sql
+INSERT INTO ticket_custom
+   (ticket, name, value)
+   SELECT 
+      id AS ticket,
+      'request_source' AS name,
+      'None' AS value
+   FROM ticket 
+   WHERE id NOT IN (
+      SELECT ticket FROM ticket_custom
+   );
+}}}
+
+If you added multiple custom fields at different points in time, you should be more specific in the subquery on table {{{ticket}}} by adding the exact custom field name to the query:
+
+{{{
+#!sql
+INSERT INTO ticket_custom
+   (ticket, name, value)
+   SELECT 
+      id AS ticket,
+      'request_source' AS name,
+      'None' AS value
+   FROM ticket 
+   WHERE id NOT IN (
+      SELECT ticket FROM ticket_custom WHERE name = 'request_source'
+   );
+}}}
+
 ----
 See also: TracTickets, TracIni