Changes between Version 3 and Version 4 of 1.3/TracTicketsCustomFields

Timestamp:

Apr 12, 2017, 6:32:15 PM (7 years ago)

Author:

Ryan J Ollos

Comment:

Minor edits.

1.3/TracTicketsCustomFields

@@ -4 +4 @@
 == Configuration
 
-Configuring custom ticket fields is done in the [wiki:TracIni trac.ini] file. All field definitions should be under a section named `[ticket-custom]`.
+Configuring custom ticket fields in the [TracIni#ticket-custom-section "[ticket-custom]"] section of trac.ini.
 
 The syntax of each field definition is:
@@ -20 +20 @@
    * label: Descriptive label.
    * value: Default value.
-   * order: Sort order placement; this determines relative placement in forms with respect to other custom fields.
+   * order: Sort order placement relative to other custom fields.
    * max_size: Maximum allowed size in characters (//Since 1.3.2//).
    * format: One of: 
      * `plain` for plain text 
-     * `wiki` to interpret the content as WikiFormatting
+     * `wiki` for [WikiFormatting wiki formatted] content
      * `reference` to treat the content as a queryable value
      * `list` to interpret the content as a list of queryable values, separated by whitespace
@@ -85 +85 @@
 test_five = radio
 test_five.label = Radio buttons are fun
-test_five.options = uno|dos|tres|cuatro|cinco
+test_five.options = |uno|dos|tres|cuatro|cinco
 test_five.value = dos
 
@@ -110 +110 @@
 }}}
 
-'''Note''': To make a `select` type field optional, specify a leading `|` in the `fieldname.options` option.
+'''Note''': To make a `select` type field optional, specify a leading `|` in `fieldname.options` (e.g. `test_five`).
 
 === Reports Involving Custom Fields
@@ -144 +144 @@
 Note in particular the `LEFT OUTER JOIN` statement here.
 
-Note that if your config file uses an '''uppercase''' name:
+Note that option names in trac.ini are case-insensitive, so even if your option name includes uppercase characters:
 {{{#!ini
 [ticket-custom]
-
 Progress_Type = text
 }}}
-you would use '''lowercase''' in the SQL: `AND c.name = 'progress_type'`.
+you must use '''lowercase''' in the SQL: `AND c.name = 'progress_type'`.
 
 === Updating the database