Changes between Version 33 and Version 34 of TracTicketsCustomFields
- Timestamp:
- Nov 14, 2016, 1:30:41 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTicketsCustomFields
v33 v34 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 … … 21 20 * label: Descriptive label. 22 21 * value: Default value. 23 * 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. 24 23 * format: One of: 25 24 * `plain` for plain text … … 29 28 * '''checkbox''': A boolean value check box. 30 29 * label: Descriptive label. 31 * value: Default value :0 or 1.30 * value: Default value, 0 or 1. 32 31 * order: Sort order placement. 33 32 * '''select''': Drop-down select box. Uses a list of values. … … 39 38 * label: Descriptive label. 40 39 * options: List of values, separated by '''|''' (vertical pipe). 41 * value: Default value (one of the values from options).40 * value: Default value, one of the values from options. 42 41 * order: Sort order placement. 43 42 * '''textarea''': Multi-line text area. 44 43 * label: Descriptive label. 45 44 * value: Default text. 46 * cols: Width in columns 45 * cols: Width in columns. //(Removed in 1.1.2)// 47 46 * rows: Height in lines. 48 47 * order: Sort order placement. 49 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. 50 59 51 60 Macros will be expanded when rendering `textarea` fields with format `wiki`, but not when rendering `text` fields with format `wiki`. … … 83 92 test_six.cols = 60 84 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 85 109 }}} 86 110 87 '''Note''': To make entering an option fora `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. 88 112 89 113 === Reports Involving Custom Fields … … 99 123 ORDER BY p.value 100 124 }}} 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. 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. 103 126 104 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:
