Changes between Version 2 and Version 3 of TracTicketsCustomFields
- Timestamp:
- 12/24/20 10:50:35 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTicketsCustomFields
v2 v3 4 4 == Configuration 5 5 6 Configur ecustom ticket fields in the [TracIni#ticket-custom-section "[ticket-custom]"] section of trac.ini.6 Configuring custom ticket fields in the [TracIni#ticket-custom-section "[ticket-custom]"] section of trac.ini. 7 7 8 8 The syntax of each field definition is: … … 15 15 The example below should help to explain the syntax. 16 16 17 === Field Names18 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 * cc22 * changetime23 * col24 * comment25 * component26 * desc27 * description28 * format29 * group30 * groupdesc31 * id32 * keywords33 * max34 * milestone35 * or36 * order37 * owner38 * page39 * priority40 * report41 * reporter42 * resolution43 * row44 * severity45 * status46 * summary47 * time48 * type49 * verbose50 * version51 52 17 === Available Field Types and Options 53 18 … … 57 22 * order: Sort order placement relative to other custom fields. 58 23 * 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 61 26 * `wiki` for [WikiFormatting wiki formatted] content 62 27 * `reference` to treat the content as a queryable value