Changes between Version 3 and Version 4 of TracTicketsCustomFields
- Timestamp:
- 02/01/17 00:38:00 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTicketsCustomFields
v3 v4 1 = Custom Ticket Fields =2 Trac supports adding custom, user-defined fields to the ticket module. Using custom fields,you can add typed, site-specific properties to tickets.1 = Custom Ticket Fields 2 Trac supports adding custom, user-defined fields to the ticket module. With custom fields you can add typed, site-specific properties to tickets. 3 3 4 == Configuration == 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 === Available Field Types and Options === 17 === Available Field Types and Options 18 16 19 * '''text''': A simple (one line) text field. 17 20 * label: Descriptive label. 18 21 * value: Default value. 19 * order: Sort order placement . (Determines relative placement in forms with respect to other custom fields.)22 * order: Sort order placement; this determines relative placement in forms with respect to other custom fields. 20 23 * format: One of: 21 24 * `plain` for plain text … … 25 28 * '''checkbox''': A boolean value check box. 26 29 * label: Descriptive label. 27 * value: Default value (0 or 1).30 * value: Default value, 0 or 1. 28 31 * order: Sort order placement. 29 32 * '''select''': Drop-down select box. Uses a list of values. … … 35 38 * label: Descriptive label. 36 39 * options: List of values, separated by '''|''' (vertical pipe). 37 * value: Default value (one of the values from options).40 * value: Default value, one of the values from options. 38 41 * order: Sort order placement. 39 42 * '''textarea''': Multi-line text area. 40 43 * label: Descriptive label. 41 44 * value: Default text. 42 * cols: Width in columns 45 * cols: Width in columns. //(Removed in 1.1.2)// 43 46 * rows: Height in lines. 44 47 * order: Sort order placement. 45 48 * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting. 49 * '''time''': Date and time picker. (''Since 1.1.1.'') 50 * label: Descriptive label. 51 * value: Default date. 52 * order: Sort order placement. 53 * format: One of: 54 * `relative` for relative dates. 55 * `date` for absolute dates. 56 * `datetime` for absolute date and time values. 57 58 If the `label` is not specified, it will be created by capitalizing the custom field name and replacing underscores with whitespaces. 46 59 47 60 Macros will be expanded when rendering `textarea` fields with format `wiki`, but not when rendering `text` fields with format `wiki`. 48 61 49 === Sample Config === 50 {{{ 62 === Sample Configuration 63 64 {{{#!ini 51 65 [ticket-custom] 52 66 … … 78 92 test_six.cols = 60 79 93 test_six.rows = 30 94 95 test_seven = time 96 test_seven.label = A relative date 97 test_seven.format = relative 98 test_seven.value = now 99 100 test_eight = time 101 test_eight.label = An absolute date 102 test_eight.format = date 103 test_eight.value = yesterday 104 105 test_nine = time 106 test_nine.label = A date and time 107 test_nine.format = datetime 108 test_nine.value = in 2 hours 80 109 }}} 81 110 82 '' Note: To make entering an option for a `select` type field optional, specify a leading `|` in the `fieldname.options` option.''111 '''Note''': To make a `select` type field optional, specify a leading `|` in the `fieldname.options` option. 83 112 84 === Reports Involving Custom Fields ===113 === Reports Involving Custom Fields 85 114 86 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`. 87 116 88 {{{ 89 #!sql 117 {{{#!sql 90 118 SELECT p.value AS __color__, 91 119 id AS ticket, summary, owner, c.value AS progress … … 95 123 ORDER BY p.value 96 124 }}} 97 '''Note''' that 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's all you want, you're set.125 '''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. 98 126 99 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. 100 {{{ 101 #!sql 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: 128 {{{#!sql 102 129 SELECT p.value AS __color__, 103 130 id AS ticket, summary, component, version, milestone, severity, … … 106 133 changetime AS _changetime, description AS _description, 107 134 reporter AS _reporter, 108 (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 109 136 FROM ticket t 110 137 LEFT OUTER JOIN ticket_custom c ON (t.id = c.ticket AND c.name = 'progress') … … 116 143 Note in particular the `LEFT OUTER JOIN` statement here. 117 144 118 Note that if your config file uses an uppercase name, e.g.,119 {{{ 145 Note that if your config file uses an '''uppercase''' name: 146 {{{#!ini 120 147 [ticket-custom] 121 148 122 149 Progress_Type = text 123 150 }}} 124 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'`. 125 152 126 === Updating the database ===153 === Updating the database 127 154 128 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: 129 156 130 {{{ 131 #!sql 157 {{{#!sql 132 158 INSERT INTO ticket_custom 133 159 (ticket, name, value) … … 144 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: 145 171 146 {{{ 147 #!sql 172 {{{#!sql 148 173 INSERT INTO ticket_custom 149 174 (ticket, name, value)
