Edgewall Software

Changes between Version 3 and Version 4 of 1.3/TracTicketsCustomFields


Ignore:
Timestamp:
Apr 12, 2017, 6:32:15 PM (5 years ago)
Author:
Ryan J Ollos
Comment:

Minor edits.

Legend:

Unmodified
Added
Removed
Modified
  • 1.3/TracTicketsCustomFields

    v3 v4  
    44== Configuration
    55
    6 Configuring custom ticket fields is done in the [wiki:TracIni trac.ini] file. All field definitions should be under a section named `[ticket-custom]`.
     6Configuring custom ticket fields in the [TracIni#ticket-custom-section "[ticket-custom]"] section of trac.ini.
    77
    88The syntax of each field definition is:
     
    2020   * label: Descriptive label.
    2121   * value: Default value.
    22    * order: Sort order placement; this determines relative placement in forms with respect to other custom fields.
     22   * order: Sort order placement relative to other custom fields.
    2323   * max_size: Maximum allowed size in characters (//Since 1.3.2//).
    2424   * format: One of:
    2525     * `plain` for plain text
    26      * `wiki` to interpret the content as WikiFormatting
     26     * `wiki` for [WikiFormatting wiki formatted] content
    2727     * `reference` to treat the content as a queryable value
    2828     * `list` to interpret the content as a list of queryable values, separated by whitespace
     
    8585test_five = radio
    8686test_five.label = Radio buttons are fun
    87 test_five.options = uno|dos|tres|cuatro|cinco
     87test_five.options = |uno|dos|tres|cuatro|cinco
    8888test_five.value = dos
    8989
     
    110110}}}
    111111
    112 '''Note''': To make a `select` type field optional, specify a leading `|` in the `fieldname.options` option.
     112'''Note''': To make a `select` type field optional, specify a leading `|` in `fieldname.options` (e.g. `test_five`).
    113113
    114114=== Reports Involving Custom Fields
     
    144144Note in particular the `LEFT OUTER JOIN` statement here.
    145145
    146 Note that if your config file uses an '''uppercase''' name:
     146Note that option names in trac.ini are case-insensitive, so even if your option name includes uppercase characters:
    147147{{{#!ini
    148148[ticket-custom]
    149 
    150149Progress_Type = text
    151150}}}
    152 you would use '''lowercase''' in the SQL: `AND c.name = 'progress_type'`.
     151you must use '''lowercase''' in the SQL: `AND c.name = 'progress_type'`.
    153152
    154153=== Updating the database