Changes between Version 1 and Version 2 of TracTicketsCustomFields
- Timestamp:
- Dec 3, 2016, 9:48:27 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTicketsCustomFields
v1 v2 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 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 6 … … 13 13 The example below should help to explain the syntax. 14 14 15 === Available Field Types and Options ===15 === Available Field Types and Options 16 16 * '''text''': A simple (one line) text field. 17 17 * label: Descriptive label. 18 18 * value: Default value. 19 * order: Sort order placement . (Determines relative placement in forms with respect to other custom fields.)19 * order: Sort order placement; this determines relative placement in forms with respect to other custom fields. 20 20 * format: One of: 21 21 * `plain` for plain text … … 25 25 * '''checkbox''': A boolean value check box. 26 26 * label: Descriptive label. 27 * value: Default value (0 or 1).27 * value: Default value, 0 or 1. 28 28 * order: Sort order placement. 29 29 * '''select''': Drop-down select box. Uses a list of values. … … 35 35 * label: Descriptive label. 36 36 * options: List of values, separated by '''|''' (vertical pipe). 37 * value: Default value (one of the values from options).37 * value: Default value, one of the values from options. 38 38 * order: Sort order placement. 39 39 * '''textarea''': Multi-line text area. 40 40 * label: Descriptive label. 41 41 * value: Default text. 42 * cols: Width in columns 42 * cols: Width in columns. //(Removed in 1.1.2)// 43 43 * rows: Height in lines. 44 44 * order: Sort order placement. 45 45 * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting. 46 * '''time''': Date and time picker. (''Since 1.1.1.'') 47 * label: Descriptive label. 48 * value: Default date. 49 * order: Sort order placement. 50 * format: One of: 51 * `relative` for relative dates. 52 * `date` for absolute dates. 53 * `datetime` for absolute date and time values. 54 55 If the `label` is not specified, it will be created by capitalizing the custom field name and replacing underscores with whitespaces. 46 56 47 57 Macros will be expanded when rendering `textarea` fields with format `wiki`, but not when rendering `text` fields with format `wiki`. 48 58 49 === Sample Config ===59 === Sample Config 50 60 {{{ 51 61 [ticket-custom] … … 78 88 test_six.cols = 60 79 89 test_six.rows = 30 90 91 test_seven = time 92 test_seven.label = A relative date 93 test_seven.format = relative 94 test_seven.value = now 95 96 test_eight = time 97 test_eight.label = An absolute date 98 test_eight.format = date 99 test_eight.value = yesterday 100 101 test_nine = time 102 test_nine.label = A date and time 103 test_nine.format = datetime 104 test_nine.value = in 2 hours 80 105 }}} 81 106 82 '' Note: To make entering an option for a `select` type field optional, specify a leading `|` in the `fieldname.options` option.''107 '''Note''': To make a `select` type field optional, specify a leading `|` in the `fieldname.options` option. 83 108 84 === Reports Involving Custom Fields ===109 === Reports Involving Custom Fields 85 110 86 111 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`. … … 95 120 ORDER BY p.value 96 121 }}} 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.122 '''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 123 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 .124 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 125 {{{ 101 126 #!sql … … 122 147 Progress_Type = text 123 148 }}} 124 you would use lowercase in the SQL: 149 you would use lowercase in the SQL: `AND c.name = 'progress_type'` 125 150 126 === Updating the database ===151 === Updating the database 127 152 128 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:
