Changes between Version 6 and Version 7 of 1.1/TracTicketsCustomFields
- Timestamp:
- Jan 13, 2015, 4:37:55 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
1.1/TracTicketsCustomFields
v6 v7 20 20 * format: One of: 21 21 * `plain` for plain text 22 * `wiki` to interpret the content as WikiFormatting (''since 0.11.3'')22 * `wiki` to interpret the content as WikiFormatting 23 23 * `reference` to treat the content as a queryable value (''since 1.0'') 24 24 * `list` to interpret the content as a list of queryable values, separated by whitespace (''since 1.0'') … … 40 40 * label: Descriptive label. 41 41 * value: Default text. 42 * cols: Width in columns . //(Removed in 1.1.2)//42 * cols: Width in columns 43 43 * rows: Height in lines. 44 44 * order: Sort order placement. 45 * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting. (''since 0.11.3'')45 * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting. 46 46 * '''time''': Date (& time) picker. (''Since 1.1.1.'') 47 47 * label: Descriptive label. … … 54 54 55 55 If the `label` is not specified it will be created by capitalizing the custom field name and replacing underscores with whitespaces. 56 57 Macros will be expanded when rendering `textarea` fields with format `wiki`, but not when rendering `text` fields with format `wiki`. 56 58 57 59 === Sample Config === … … 139 141 Note in particular the `LEFT OUTER JOIN` statement here. 140 142 143 Note that if your config file uses an uppercase name, e.g., 144 {{{ 145 [ticket-custom] 146 147 Progress_Type = text 148 }}} 149 you would use lowercase in the SQL: `AND c.name = 'progress_type'` 150 141 151 === Updating the database === 142 152