![(please configure [header_logo] section in trac.ini)](https://lpsc.in2p3.fr/trac/chrome/common/logo_LPSC.png){kind=logo}
Changes between Version 9 and Version 10 of TracTicketsCustomFields
- Timestamp:
- 14/06/2017 12:47:21 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTicketsCustomFields
v9 v10 3 3 4 4 == Configuration 5 5 6 Configuring custom ticket fields is done in the [wiki:TracIni trac.ini] file. All field definitions should be under a section named `[ticket-custom]`. 6 7 … … 11 12 ... 12 13 }}} 14 13 15 The example below should help to explain the syntax. 14 16 15 17 === Available Field Types and Options 18 16 19 * '''text''': A simple (one line) text field. 17 20 * label: Descriptive label. … … 57 60 Macros will be expanded when rendering `textarea` fields with format `wiki`, but not when rendering `text` fields with format `wiki`. 58 61 59 === Sample Config 60 {{{ 62 === Sample Configuration 63 64 {{{#!ini 61 65 [ticket-custom] 62 66 … … 111 115 Custom ticket fields are stored in the `ticket_custom` table, not in the `ticket` table. So to display the values from custom fields in a report, you will need a join on the 2 tables. Let's use an example with a custom ticket field called `progress`. 112 116 113 {{{ 114 #!sql 117 {{{#!sql 115 118 SELECT p.value AS __color__, 116 119 id AS ticket, summary, owner, c.value AS progress … … 123 126 124 127 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: 125 {{{ 126 #!sql 128 {{{#!sql 127 129 SELECT p.value AS __color__, 128 130 id AS ticket, summary, component, version, milestone, severity, … … 131 133 changetime AS _changetime, description AS _description, 132 134 reporter AS _reporter, 133 (CASE WHEN c.value = '0' THEN 'None' ELSE c.value END) AS progress135 (CASE WHEN c.value = '0' THEN 'None' ELSE c.value END) AS progress 134 136 FROM ticket t 135 137 LEFT OUTER JOIN ticket_custom c ON (t.id = c.ticket AND c.name = 'progress') … … 141 143 Note in particular the `LEFT OUTER JOIN` statement here. 142 144 143 Note that if your config file uses an uppercase name, e.g.,144 {{{ 145 Note that if your config file uses an '''uppercase''' name: 146 {{{#!ini 145 147 [ticket-custom] 146 148 147 149 Progress_Type = text 148 150 }}} 149 you would use lowercase in the SQL: `AND c.name = 'progress_type'`151 you would use '''lowercase''' in the SQL: `AND c.name = 'progress_type'`. 150 152 151 153 === Updating the database 152 154 153 As noted above, any tickets created before a custom field has been defined will not have a value for that field. Here 's a bit of SQL (tested with SQLite) that you can run directly on the Trac database to set an initial value for custom ticket fields. Inserts the default value of 'None' into a custom field called 'request_source' for all tickets that have no existing value:155 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: 154 156 155 {{{ 156 #!sql 157 {{{#!sql 157 158 INSERT INTO ticket_custom 158 159 (ticket, name, value) … … 169 170 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: 170 171 171 {{{ 172 #!sql 172 {{{#!sql 173 173 INSERT INTO ticket_custom 174 174 (ticket, name, value)
