Changes between Version 5 and Version 6 of TracTicketsCustomFields


Ignore:
Timestamp:
09/24/20 14:30:47 (4 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracTicketsCustomFields

    v5 v6  
    33
    44== Configuration
    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]`.
     5
     6Configure custom ticket fields in the [TracIni#ticket-custom-section "[ticket-custom]"] section of trac.ini.
    67
    78The syntax of each field definition is:
    … …  
    1112 ...
    1213}}}
     14
    1315The example below should help to explain the syntax.
    1416
     17=== Field Names
     18A 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
     20The 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
    1552=== Available Field Types and Options
     53
    1654 * '''text''': A simple (one line) text field.
    1755   * label: Descriptive label.
    1856   * value: Default value.
    19    * order: Sort order placement; this determines relative placement in forms with respect to other custom fields.
    20    * format: One of:
    21      * `plain` for plain text
    22      * `wiki` to interpret the content as WikiFormatting
    23      * `reference` to treat the content as a queryable value (''since 1.0'')
    24      * `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
    2564 * '''checkbox''': A boolean value check box.
    2665   * label: Descriptive label.
    … …  
    4079   * label: Descriptive label.
    4180   * value: Default text.
    42    * cols: Width in columns. //(Removed in 1.1.2)//
    4381   * rows: Height in lines.
    4482   * order: Sort order placement.
     83   * max_size: Maximum allowed size in characters (//Since 1.3.2//).
    4584   * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting.
    46  * '''time''': Date and time picker. (''Since 1.1.1.'')
     85 * '''time''': Date and time picker. (//Since 1.1.1//)
    4786   * label: Descriptive label.
    4887   * value: Default date.
    … …  
    5796Macros will be expanded when rendering `textarea` fields with format `wiki`, but not when rendering `text` fields with format `wiki`.
    5897
    59 === Sample Config
    60 {{{
     98=== Sample Configuration
     99
     100{{{#!ini
    61101[ticket-custom]
    62102
    … …  
    80120test_five = radio
    81121test_five.label = Radio buttons are fun
    82 test_five.options = uno|dos|tres|cuatro|cinco
     122test_five.options = |uno|dos|tres|cuatro|cinco
    83123test_five.value = dos
    84124
    … …  
    105145}}}
    106146
    107 '''Note''': To make 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`).
    108148
    109149=== Reports Involving Custom Fields
    … …  
    111151Custom 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`.
    112152
    113 {{{
    114 #!sql
     153{{{#!sql
    115154SELECT p.value AS __color__,
    116155   id AS ticket, summary, owner, c.value AS progress
    … …  
    123162
    124163However, 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
     164{{{#!sql
    127165SELECT p.value AS __color__,
    128166   id AS ticket, summary, component, version, milestone, severity,
    … …  
    131169   changetime AS _changetime, description AS _description,
    132170   reporter AS _reporter,
    133   (CASE WHEN c.value = '0' THEN 'None' ELSE c.value END) AS progress
     171   (CASE WHEN c.value = '0' THEN 'None' ELSE c.value END) AS progress
    134172  FROM ticket t
    135173     LEFT OUTER JOIN ticket_custom c ON (t.id = c.ticket AND c.name = 'progress')
    … …  
    141179Note in particular the `LEFT OUTER JOIN` statement here.
    142180
    143 Note that if your config file uses an uppercase name, e.g.,
    144 {{{
     181Note that option names in trac.ini are case-insensitive, so even if your option name includes uppercase characters:
     182{{{#!ini
    145183[ticket-custom]
    146 
    147184Progress_Type = text
    148185}}}
    149 you would use lowercase in the SQL: `AND c.name = 'progress_type'`
    150 
    151 === Updating the database
    152 
    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:
    154 
    155 {{{
    156 #!sql
    157 INSERT INTO ticket_custom
    158    (ticket, name, value)
    159    SELECT
    160       id AS ticket,
    161       'request_source' AS name,
    162       'None' AS value
    163    FROM ticket
    164    WHERE id NOT IN (
    165       SELECT ticket FROM ticket_custom
    166    );
    167 }}}
    168 
    169 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 {{{
    172 #!sql
    173 INSERT INTO ticket_custom
    174    (ticket, name, value)
    175    SELECT
    176       id AS ticket,
    177       'request_source' AS name,
    178       'None' AS value
    179    FROM ticket
    180    WHERE id NOT IN (
    181       SELECT ticket FROM ticket_custom WHERE name = 'request_source'
    182    );
    183 }}}
     186you must use '''lowercase''' in the SQL: `AND c.name = 'progress_type'`.
    184187
    185188----