Changes between Version 1 and Version 2 of TracTicketsCustomFields


Ignore:
Timestamp:
Mar 27, 2008, 7:31:47 AM (12 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracTicketsCustomFields

    v1 v2  
    1717   * label: Descriptive label.
    1818   * value: Default value.
    19    * order: Sort order placement. (Determines relative placement in forms.)
     19   * order: Sort order placement. (Determines relative placement in forms with respect to other custom fields.)
    2020 * '''checkbox''': A boolean value check box.
    2121   * label: Descriptive label.
     
    2323   * order: Sort order placement.
    2424 * '''select''': Drop-down select box. Uses a list of values.
     25   * label: Descriptive label.
    2526   * options: List of values, separated by '''|''' (vertical pipe).
    26    * value: Default value (Item #, starting at 0).
     27   * value: Default value (one of the values from options).
    2728   * order: Sort order placement.
    2829 * '''radio''': Radio buttons. Essentially the same as '''select'''.
     
    5657test_four.label = My selectbox
    5758test_four.options = one|two|third option|four
    58 test_four.value = 2
     59test_four.value = two
    5960
    6061test_five = radio
     
    7071}}}
    7172
    72 ''Note: To make an entering an option for a `select` type field optional, specify a leading `|` in the `fieldname.options` option.''
     73''Note: To make entering an option for a `select` type field optional, specify a leading `|` in the `fieldname.options` option.''
    7374
    7475=== Reports Involving Custom Fields ===
    7576
    76 The SQL required for TracReports to include custom ticket fields is relatively hard to get right. You need a `JOIN` with the `ticket_custom` field for every custom field that should be involved.
     77Custom 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`.
    7778
    78 The following example includes a custom ticket field named `progress` in the report:
     79{{{
     80#!sql
     81SELECT p.value AS __color__,
     82   id AS ticket, summary, owner, c.value AS progress
     83  FROM ticket t, enum p, ticket_custom c
     84  WHERE status IN ('assigned') AND t.id = c.ticket AND c.name = 'progress'
     85AND p.name = t.priority AND p.type = 'priority'
     86  ORDER BY p.value
     87}}}
     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.
     89
     90However, 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.
    7991{{{
    8092#!sql