Changes between Version 2 and Version 3 of TracTicketsCustomFields
- Timestamp:
- Oct 29, 2015, 1:00:54 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTicketsCustomFields
v2 v3 18 18 * value: Default value. 19 19 * 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'') 21 25 * '''checkbox''': A boolean value check box. 22 26 * label: Descriptive label. … … 36 40 * label: Descriptive label. 37 41 * value: Default text. 38 * cols: Width in columns .42 * cols: Width in columns 39 43 * rows: Height in lines. 40 44 * order: Sort order placement. 41 45 * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting. (''since 0.11.3'') 46 47 Macros will be expanded when rendering `textarea` fields with format `wiki`, but not when rendering `text` fields with format `wiki`. 42 48 43 49 === Sample Config === … … 110 116 Note in particular the `LEFT OUTER JOIN` statement here. 111 117 118 Note that if your config file uses an uppercase name, e.g., 119 {{{ 120 [ticket-custom] 121 122 Progress_Type = text 123 }}} 124 you would use lowercase in the SQL: `AND c.name = 'progress_type'` 125 112 126 === Updating the database === 113 127