Changes between Initial Version and Version 1 of TracTicketsCustomFields


Ignore:
Timestamp:
Jul 30, 2021, 7:40:25 AM (16 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracTicketsCustomFields

    v1 v1  
     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.
     3
     4== Configuration
     5
     6Configure custom ticket fields in the [TracIni#ticket-custom-section "[ticket-custom]"] section of trac.ini.
     7
     8The syntax of each field definition is:
     9{{{
     10 FIELD_NAME = TYPE
     11 (FIELD_NAME.OPTION = VALUE)
     12 ...
     13}}}
     14
     15The example below should help to explain the syntax.
     16
     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
     54 * '''text''': A simple (one line) text field.
     55   * label: Descriptive label.
     56   * value: Default value.
     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
     64   * ticketlink_query: Query for linkifying ticket values.
     65     Not applicable for format `plain` and `wiki`.
     66 * '''checkbox''': A boolean value check box.
     67   * label: Descriptive label.
     68   * value: Default value, 0 or 1.
     69   * order: Sort order placement.
     70   * ticketlink_query: Query for linkifying ticket values.
     71 * '''select''': Drop-down select box. Uses a list of values.
     72   * label: Descriptive label.
     73   * options: List of values, separated by '''|''' (vertical pipe).
     74   * value: Default value (one of the values from options).
     75   * order: Sort order placement.
     76   * ticketlink_query: Query for linkifying ticket values.
     77 * '''radio''': Radio buttons. Essentially the same as '''select'''.
     78   * label: Descriptive label.
     79   * options: List of values, separated by '''|''' (vertical pipe).
     80   * value: Default value, one of the values from options.
     81   * order: Sort order placement.
     82   * ticketlink_query: Query for linkifying ticket values.
     83 * '''textarea''': Multi-line text area.
     84   * label: Descriptive label.
     85   * value: Default text.
     86   * rows: Height in lines.
     87   * order: Sort order placement.
     88   * max_size: Maximum allowed size in characters (//Since 1.3.2//).
     89   * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting.
     90 * '''time''': Date and time picker. (//Since 1.1.1//)
     91   * label: Descriptive label.
     92   * value: Default date.
     93   * order: Sort order placement.
     94   * format: One of:
     95     * `relative` for relative dates.
     96     * `date` for absolute dates.
     97     * `datetime` for absolute date and time values.
     98
     99If the `label` is not specified, it will be created by capitalizing the custom field name and replacing underscores with whitespaces.
     100
     101Macros will be expanded when rendering `textarea` fields with format `wiki`, but not when rendering `text` fields with format `wiki`.
     102
     103For applicable fields, the `ticketlink_query` option
     104overrides [[TracIni#query-ticketlink_query-option|"[query] ticketlink_query"]], and the format is the same as
     105that option. When the `ticketlink_query` option
     106is not specified, `[query]` `ticketlink_query` is used to
     107linkify the field.
     108
     109=== Sample Configuration
     110
     111{{{#!ini
     112[ticket-custom]
     113
     114test_one = text
     115test_one.label = Just a text box
     116
     117test_two = text
     118test_two.label = Another text-box
     119test_two.value = Default [mailto:joe@nospam.com owner]
     120test_two.format = wiki
     121
     122test_three = checkbox
     123test_three.label = Some checkbox
     124test_three.value = 1
     125
     126test_four = select
     127test_four.label = My selectbox
     128test_four.options = one|two|third option|four
     129test_four.value = two
     130
     131test_five = radio
     132test_five.label = Radio buttons are fun
     133test_five.options = |uno|dos|tres|cuatro|cinco
     134test_five.value = dos
     135
     136test_six = textarea
     137test_six.label = This is a large textarea
     138test_six.value = Default text
     139test_six.cols = 60
     140test_six.rows = 30
     141
     142test_seven = time
     143test_seven.label = A relative date
     144test_seven.format = relative
     145test_seven.value = now
     146
     147test_eight = time
     148test_eight.label = An absolute date
     149test_eight.format = date
     150test_eight.value = yesterday
     151
     152test_nine = time
     153test_nine.label = A date and time
     154test_nine.format = datetime
     155test_nine.value = in 2 hours
     156}}}
     157
     158'''Note''': To make a `select` type field optional, specify a leading `|` in `fieldname.options` (e.g. `test_five`).
     159
     160=== Reports Involving Custom Fields
     161
     162Custom 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`.
     163
     164{{{#!sql
     165SELECT p.value AS __color__,
     166   id AS ticket, summary, owner, c.value AS progress
     167  FROM ticket t, enum p, ticket_custom c
     168  WHERE status IN ('assigned') AND t.id = c.ticket AND c.name = 'progress'
     169AND p.name = t.priority AND p.type = 'priority'
     170  ORDER BY p.value
     171}}}
     172'''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.
     173
     174However, 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:
     175{{{#!sql
     176SELECT p.value AS __color__,
     177   id AS ticket, summary, component, version, milestone, severity,
     178   (CASE status WHEN 'assigned' THEN owner||' *' ELSE owner END) AS owner,
     179   time AS created,
     180   changetime AS _changetime, description AS _description,
     181   reporter AS _reporter,
     182   (CASE WHEN c.value = '0' THEN 'None' ELSE c.value END) AS progress
     183  FROM ticket t
     184     LEFT OUTER JOIN ticket_custom c ON (t.id = c.ticket AND c.name = 'progress')
     185     JOIN enum p ON p.name = t.priority AND p.type='priority'
     186  WHERE status IN ('new', 'assigned', 'reopened')
     187  ORDER BY p.value, milestone, severity, time
     188}}}
     189
     190Note in particular the `LEFT OUTER JOIN` statement here.
     191
     192Note that option names in trac.ini are case-insensitive, so even if your option name includes uppercase characters:
     193{{{#!ini
     194[ticket-custom]
     195Progress_Type = text
     196}}}
     197you must use '''lowercase''' in the SQL: `AND c.name = 'progress_type'`.
     198
     199----
     200See also: TracTickets, TracIni