![[MC-04 logo]](/mc-04/chrome/site/logo.png){kind=logo}
Changes between Version 2 and Version 3 of TracTicketsCustomFields
- Timestamp:
- Nov 26, 2022, 2:16:40 PM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTicketsCustomFields
v2 v3 1 1 = Custom Ticket Fields 2 3 Trac supports adding custom, user-defined fields to the ticket module. Using custom fields, you can add typed, site-specific properties to tickets. 2 Trac supports adding custom, user-defined fields to the ticket module. With custom fields you can add typed, site-specific properties to tickets. 4 3 5 4 == Configuration 6 5 7 Configur ing custom ticket fields is done in the [wiki:TracIni trac.ini] file. All field definitions should be under a section named `[ticket-custom]`.6 Configure custom ticket fields in the [TracIni#ticket-custom-section "[ticket-custom]"] section of trac.ini. 8 7 9 8 The syntax of each field definition is: … … 16 15 The example below should help to explain the syntax. 17 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 18 52 === Available Field Types and Options 19 53 … … 21 55 * label: Descriptive label. 22 56 * value: Default value. 23 * order: Sort order placement. Determines relative placement in forms with respect to other custom fields. 24 * format: One of: 25 * `plain` for plain text 26 * `wiki` to interpret the content as WikiFormatting 27 * `reference` to treat the content as a queryable value (''since 1.0'') 28 * `list` to interpret the content as a list of queryable values, separated by whitespace (''since 1.0'') 57 * order: Sort order placement relative to other custom fields. 58 * max_size: Maximum allowed size in characters (//Since 1.3.2//). 59 * format: One of: 60 * `plain` for plain text 61 * `wiki` for [WikiFormatting wiki formatted] content 62 * `reference` to treat the content as a queryable value 63 * `list` to interpret the content as a list of queryable values, separated by whitespace 29 64 * '''checkbox''': A boolean value check box. 30 65 * label: Descriptive label. 31 * value: Default value :0 or 1.66 * value: Default value, 0 or 1. 32 67 * order: Sort order placement. 33 68 * '''select''': Drop-down select box. Uses a list of values. … … 39 74 * label: Descriptive label. 40 75 * options: List of values, separated by '''|''' (vertical pipe). 41 * value: Default value (one of the values from options).76 * value: Default value, one of the values from options. 42 77 * order: Sort order placement. 43 78 * '''textarea''': Multi-line text area. 44 79 * label: Descriptive label. 45 80 * value: Default text. 46 * cols: Width in columns47 81 * rows: Height in lines. 48 82 * order: Sort order placement. 83 * max_size: Maximum allowed size in characters (//Since 1.3.2//). 49 84 * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting. 85 * '''time''': Date and time picker. (//Since 1.1.1//) 86 * label: Descriptive label. 87 * value: Default date. 88 * order: Sort order placement. 89 * format: One of: 90 * `relative` for relative dates. 91 * `date` for absolute dates. 92 * `datetime` for absolute date and time values. 93 94 If the `label` is not specified, it will be created by capitalizing the custom field name and replacing underscores with whitespaces. 50 95 51 96 Macros will be expanded when rendering `textarea` fields with format `wiki`, but not when rendering `text` fields with format `wiki`. … … 75 120 test_five = radio 76 121 test_five.label = Radio buttons are fun 77 test_five.options = uno|dos|tres|cuatro|cinco122 test_five.options = |uno|dos|tres|cuatro|cinco 78 123 test_five.value = dos 79 124 … … 83 128 test_six.cols = 60 84 129 test_six.rows = 30 130 131 test_seven = time 132 test_seven.label = A relative date 133 test_seven.format = relative 134 test_seven.value = now 135 136 test_eight = time 137 test_eight.label = An absolute date 138 test_eight.format = date 139 test_eight.value = yesterday 140 141 test_nine = time 142 test_nine.label = A date and time 143 test_nine.format = datetime 144 test_nine.value = in 2 hours 85 145 }}} 86 146 87 '''Note''': To make entering an option for a `select` type field optional, specify a leading `|` in the `fieldname.options` option.147 '''Note''': To make a `select` type field optional, specify a leading `|` in `fieldname.options` (e.g. `test_five`). 88 148 89 149 === Reports Involving Custom Fields … … 99 159 ORDER BY p.value 100 160 }}} 101 102 '''Note''': This will only show tickets that have progress set in them, which is '''not the same as showing all tickets'''. If you created this custom ticket field ''after'' you have already created some tickets, they will not have that field defined, and thus they will never show up on this ticket query. If you go back and modify those tickets, the field will be defined, and they will appear in the query. If that is all that is required, you're set. 161 '''Note''': This will only show tickets that have progress set in them. This is '''not the same as showing all tickets'''. If you created this custom ticket field ''after'' you have already created some tickets, they will not have that field defined, and thus they will never show up on this ticket query. If you go back and modify those tickets, the field will be defined, and they will appear in the query. 103 162 104 163 However, if you want to show all ticket entries (with progress defined and without), you need to use a `JOIN` for every custom field that is in the query: … … 120 179 Note in particular the `LEFT OUTER JOIN` statement here. 121 180 122 Note that if your config file uses an '''uppercase''' name:181 Note that option names in trac.ini are case-insensitive, so even if your option name includes uppercase characters: 123 182 {{{#!ini 124 183 [ticket-custom] 125 126 184 Progress_Type = text 127 185 }}} 128 you would use '''lowercase''' in the SQL: `AND c.name = 'progress_type'`. 129 130 === Updating the database 131 132 As noted above, any tickets created before a custom field has been defined will not have a value for that field. Here is some SQL (tested with SQLite) that you can run directly on the Trac database to set an initial value for custom ticket fields. It inserts the default value of 'None' into a custom field called 'request_source' for all tickets that have no existing value: 133 134 {{{#!sql 135 INSERT INTO ticket_custom 136 (ticket, name, value) 137 SELECT 138 id AS ticket, 139 'request_source' AS name, 140 'None' AS value 141 FROM ticket 142 WHERE id NOT IN ( 143 SELECT ticket FROM ticket_custom 144 ); 145 }}} 146 147 If you added multiple custom fields at different points in time, you should be more specific in the subquery on table {{{ticket}}} by adding the exact custom field name to the query: 148 149 {{{#!sql 150 INSERT INTO ticket_custom 151 (ticket, name, value) 152 SELECT 153 id AS ticket, 154 'request_source' AS name, 155 'None' AS value 156 FROM ticket 157 WHERE id NOT IN ( 158 SELECT ticket FROM ticket_custom WHERE name = 'request_source' 159 ); 160 }}} 186 you must use '''lowercase''' in the SQL: `AND c.name = 'progress_type'`. 161 187 162 188 ----
