Changes between Version 4 and Version 5 of TracTicketsCustomFields
- Timestamp:
- Feb 1, 2021, 2:06:05 PM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTicketsCustomFields
v4 v5 4 4 == Configuration 5 5 6 Configur ingcustom ticket fields in the [TracIni#ticket-custom-section "[ticket-custom]"] section of trac.ini.6 Configure 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 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 17 52 === Available Field Types and Options 18 53 … … 22 57 * order: Sort order placement relative to other custom fields. 23 58 * max_size: Maximum allowed size in characters (//Since 1.3.2//). 24 * format: One of: 25 * `plain` for plain text 59 * format: One of: 60 * `plain` for plain text 26 61 * `wiki` for [WikiFormatting wiki formatted] content 27 62 * `reference` to treat the content as a queryable value