Changes between Version 2 and Version 3 of TracTicketsCustomFields


Ignore:
Timestamp:
12/24/20 10:50:38 (4 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracTicketsCustomFields

    v2 v3  
    44== Configuration
    55
    6 Configure custom ticket fields in the [TracIni#ticket-custom-section "[ticket-custom]"] section of trac.ini.
     6Configuring custom ticket fields in the [TracIni#ticket-custom-section "[ticket-custom]"] section of trac.ini.
    77
    88The syntax of each field definition is:
    … …  
    1515The example below should help to explain the syntax.
    1616
    17 === Field Names
    18 A field name can only contain lowercase letters a-z, uppercase letters A-Z or digits 0-9, and must not start with a leading digit.
    19 
    20 The following field names are reserved and can not be used for custom fields:
    21 * cc
    22 * changetime
    23 * col
    24 * comment
    25 * component
    26 * desc
    27 * description
    28 * format
    29 * group
    30 * groupdesc
    31 * id
    32 * keywords
    33 * max
    34 * milestone
    35 * or
    36 * order
    37 * owner
    38 * page
    39 * priority
    40 * report
    41 * reporter
    42 * resolution
    43 * row
    44 * severity
    45 * status
    46 * summary
    47 * time
    48 * type
    49 * verbose
    50 * version
    51 
    5217=== Available Field Types and Options
    5318
    … …  
    5722   * order: Sort order placement relative to other custom fields.
    5823   * max_size: Maximum allowed size in characters (//Since 1.3.2//).
    59    * format: One of:
    60      * `plain` for plain text
     24   * format: One of: 
     25     * `plain` for plain text 
    6126     * `wiki` for [WikiFormatting wiki formatted] content
    6227     * `reference` to treat the content as a queryable value