Changes between Version 1 and Version 2 of TracTicketsCustomFields


Ignore:
Timestamp:
04/05/20 23:48:44 (5 years ago)
Author:
trac
Comment:

--

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
     2Trac supports adding custom, user-defined fields to the ticket module. With custom fields you can add typed, site-specific properties to tickets.
    33
    4 == Configuration ==
     4== Configuration
     5
    56Configuring custom ticket fields is done in the [wiki:TracIni trac.ini] file. All field definitions should be under a section named `[ticket-custom]`.
    67
    … …  
    1112 ...
    1213}}}
     14
    1315The example below should help to explain the syntax.
    1416
    15 === Available Field Types and Options ===
     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
     52=== 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. (Determines relative placement in forms with respect to other custom fields.)
     57   * order: Sort order placement; this determines relative placement in forms with respect to other custom fields.
     58   * format: One of:
     59     * `plain` for plain text
     60     * `wiki` to interpret the content as WikiFormatting
     61     * `reference` to treat the content as a queryable value (''since 1.0'')
     62     * `list` to interpret the content as a list of queryable values, separated by whitespace (''since 1.0'')
    2063 * '''checkbox''': A boolean value check box.
    2164   * label: Descriptive label.
    22    * value: Default value (0 or 1).
     65   * value: Default value, 0 or 1.
    2366   * order: Sort order placement.
    2467 * '''select''': Drop-down select box. Uses a list of values.
    … …  
    3073   * label: Descriptive label.
    3174   * options: List of values, separated by '''|''' (vertical pipe).
    32    * value: Default value (one of the values from options).
     75   * value: Default value, one of the values from options.
    3376   * order: Sort order placement.
    3477 * '''textarea''': Multi-line text area.
    3578   * label: Descriptive label.
    3679   * value: Default text.
    37    * cols: Width in columns.
     80   * cols: Width in columns. //(Removed in 1.1.2)//
    3881   * rows: Height in lines.
    3982   * order: Sort order placement.
     83   * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting.
     84 * '''time''': Date and time picker. (''Since 1.1.1.'')
     85   * label: Descriptive label.
     86   * value: Default date.
     87   * order: Sort order placement.
     88   * format: One of:
     89     * `relative` for relative dates.
     90     * `date` for absolute dates.
     91     * `datetime` for absolute date and time values.
    4092
    41 === Sample Config ===
    42 {{{
     93If the `label` is not specified, it will be created by capitalizing the custom field name and replacing underscores with whitespaces.
     94
     95Macros will be expanded when rendering `textarea` fields with format `wiki`, but not when rendering `text` fields with format `wiki`.
     96
     97=== Sample Configuration
     98
     99{{{#!ini
    43100[ticket-custom]
    44101
    … …  
    48105test_two = text
    49106test_two.label = Another text-box
    50 test_two.value = Just a default value
     107test_two.value = Default [mailto:joe@nospam.com owner]
     108test_two.format = wiki
    51109
    52110test_three = checkbox
    … …  
    69127test_six.cols = 60
    70128test_six.rows = 30
     129
     130test_seven = time
     131test_seven.label = A relative date
     132test_seven.format = relative
     133test_seven.value = now
     134
     135test_eight = time
     136test_eight.label = An absolute date
     137test_eight.format = date
     138test_eight.value = yesterday
     139
     140test_nine = time
     141test_nine.label = A date and time
     142test_nine.format = datetime
     143test_nine.value = in 2 hours
    71144}}}
    72145
    73 ''Note: To make entering an option for a `select` type field optional, specify a leading `|` in the `fieldname.options` option.''
     146'''Note''': To make a `select` type field optional, specify a leading `|` in the `fieldname.options` option.
    74147
    75 === Reports Involving Custom Fields ===
     148=== Reports Involving Custom Fields
    76149
    77150Custom 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`.
    78151
    79 {{{
    80 #!sql
     152{{{#!sql
    81153SELECT p.value AS __color__,
    82154   id AS ticket, summary, owner, c.value AS progress
    … …  
    86158  ORDER BY p.value
    87159}}}
    88 '''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.
     160'''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.
    89161
    90 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.
    91 {{{
    92 #!sql
     162However, 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:
     163{{{#!sql
    93164SELECT p.value AS __color__,
    94165   id AS ticket, summary, component, version, milestone, severity,
    … …  
    97168   changetime AS _changetime, description AS _description,
    98169   reporter AS _reporter,
    99   (CASE WHEN c.value = '0' THEN 'None' ELSE c.value END) AS progress
     170   (CASE WHEN c.value = '0' THEN 'None' ELSE c.value END) AS progress
    100171  FROM ticket t
    101172     LEFT OUTER JOIN ticket_custom c ON (t.id = c.ticket AND c.name = 'progress')
    … …  
    107178Note in particular the `LEFT OUTER JOIN` statement here.
    108179
    109 === Updating the database ===
     180Note that if your config file uses an '''uppercase''' name:
     181{{{#!ini
     182[ticket-custom]
    110183
    111 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:
    112 
    113 {{{
    114 #!sql
    115 INSERT INTO ticket_custom
    116    (ticket, name, value)
    117    SELECT
    118       id AS ticket,
    119       'request_source' AS name,
    120       'None' AS value
    121    FROM ticket
    122    WHERE id NOT IN (
    123       SELECT ticket FROM ticket_custom
    124    );
     184Progress_Type = text
    125185}}}
    126 
    127 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:
    128 
    129 {{{
    130 #!sql
    131 INSERT INTO ticket_custom
    132    (ticket, name, value)
    133    SELECT
    134       id AS ticket,
    135       'request_source' AS name,
    136       'None' AS value
    137    FROM ticket
    138    WHERE id NOT IN (
    139       SELECT ticket FROM ticket_custom WHERE name = 'request_source'
    140    );
    141 }}}
     186you would use '''lowercase''' in the SQL: `AND c.name = 'progress_type'`.
    142187
    143188----