Changes between Version 3 and Version 4 of TracTicketsCustomFields


Ignore:
Timestamp:
Nov 17, 2014, 9:39:05 PM (10 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracTicketsCustomFields

    v3 v4  
    1818   * value: Default value.
    1919   * order: Sort order placement. (Determines relative placement in forms with respect to other custom fields.)
    20    * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting. (''since 0.11.3'')
     20   * format: One of:
     21     * `plain` for plain text
     22     * `wiki` to interpret the content as WikiFormatting (''since 0.11.3'')
     23     * `reference` to treat the content as a queryable value (''since 1.0'')
     24     * `list` to interpret the content as a list of queryable values, separated by whitespace (''since 1.0'')
    2125 * '''checkbox''': A boolean value check box.
    2226   * label: Descriptive label.
    … …  
    3640   * label: Descriptive label.
    3741   * value: Default text.
    38    * cols: Width in columns.
     42   * cols: Width in columns
    3943   * rows: Height in lines.
    4044   * order: Sort order placement.
    4145   * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting. (''since 0.11.3'')
     46
     47Macros will be expanded when rendering `textarea` fields with format `wiki`, but not when rendering `text` fields with format `wiki`.
    4248
    4349=== Sample Config ===
    … …  
    110116Note in particular the `LEFT OUTER JOIN` statement here.
    111117
     118Note that if your config file uses an uppercase name, e.g.,
     119{{{
     120[ticket-custom]
     121
     122Progress_Type = text
     123}}}
     124you would use lowercase in the SQL:  `AND c.name = 'progress_type'`
     125
    112126=== Updating the database ===
    113127