Changes between Version 1 and Version 2 of TracTicketsCustomFields


Ignore:
Timestamp:
08/27/15 23:20:06 (2 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracTicketsCustomFields

    v1 v2  
    1 = カスタムチケット属性 =
    2 Trac ではチケットにユーザ定義の属性を追加できます。カスタムチケット属性を使用すると、定型で、プロジェクト特有のプロパティをチケットに持たせることができます。
     1= Custom Ticket Fields
    32
    4 == 設定方法 ==
    5 カスタムチケット属性を設定するためには、 [wiki:TracIni trac.ini] ファイルを変更します。カスタムフィールドは、 trac.ini ファイルの `[ticket-custom]` セクションに書く必要があります。
     3Trac supports adding custom, user-defined fields to the ticket module. Using custom fields, you can add typed, site-specific properties to tickets.
    64
    7 各属性の定義は以下のように記述します:
     5== Configuration
     6
     7Configuring custom ticket fields is done in the [wiki:TracIni trac.ini] file. All field definitions should be under a section named `[ticket-custom]`.
     8
     9The syntax of each field definition is:
    810{{{
    9  属性名 = タイプ
    10  (属性名.オプション = 値)
     11 FIELD_NAME = TYPE
     12 (FIELD_NAME.OPTION = VALUE)
    1113 ...
    1214}}}
    13 構文の詳細は以下の例を見てください。
    1415
    15 === 属性のタイプとオプション ===
    16  * '''text''': シンプルな(1行の)テキスト。
    17    * label: 説明となるラベル
    18    * value: デフォルト値
    19    * order: ソート時の並び順 (フォーム内での相対的位置を決定します。)
    20  * '''checkbox''': ブーリアン値をもつチェックボックス。
    21    * label: 説明となるラベル。
    22    * value: デフォルト値 (0 または 1).
    23    * order: ソート時の並び順
    24  * '''select''': ドロップダウンするリストボックス。
    25    * label: 説明となるラベル。
    26    * options: リストに表示する値を '''|''' (vertical pipe) 区切りで記述。
    27    * value: デフォルト値 (0から始まるリスト内での番号) 。
    28    * order: ソート時の並び順
    29  * '''radio''': ラジオボタン。 HTML の '''select''' 要素と同じ。
    30    * label: 説明となるラベル。
    31    * options: リストに表示する値を '''|''' (vertical pipe) 区切りで記述。
    32    * value: デフォルト値 (0から始まるリスト内での番号) 。
    33    * order: ソート時の並び順
    34  * '''textarea''': 複数行のテキストエリア。
    35    * label: 説明となるラベル。
    36    * value: デフォルトで設定されるテキスト。
    37    * cols: 入力領域のカラム幅。
    38    * rows: 入力領域の行数。
    39    * order: ソート時の並び順
     16The example below should help to explain the syntax.
    4017
    41 === サンプル ===
    42 {{{
     18=== Available Field Types and Options
     19
     20 * '''text''': A simple (one line) text field.
     21   * label: Descriptive label.
     22   * value: Default value.
     23   * order: Sort order placement. Determines relative placement in forms with respect to other custom fields.
     24   * format: One of:
     25     * `plain` for plain text
     26     * `wiki` to interpret the content as WikiFormatting
     27     * `reference` to treat the content as a queryable value (''since 1.0'')
     28     * `list` to interpret the content as a list of queryable values, separated by whitespace (''since 1.0'')
     29 * '''checkbox''': A boolean value check box.
     30   * label: Descriptive label.
     31   * value: Default value: 0 or 1.
     32   * order: Sort order placement.
     33 * '''select''': Drop-down select box. Uses a list of values.
     34   * label: Descriptive label.
     35   * options: List of values, separated by '''|''' (vertical pipe).
     36   * value: Default value (one of the values from options).
     37   * order: Sort order placement.
     38 * '''radio''': Radio buttons. Essentially the same as '''select'''.
     39   * label: Descriptive label.
     40   * options: List of values, separated by '''|''' (vertical pipe).
     41   * value: Default value (one of the values from options).
     42   * order: Sort order placement.
     43 * '''textarea''': Multi-line text area.
     44   * label: Descriptive label.
     45   * value: Default text.
     46   * cols: Width in columns
     47   * rows: Height in lines.
     48   * order: Sort order placement.
     49   * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting.
     50
     51Macros will be expanded when rendering `textarea` fields with format `wiki`, but not when rendering `text` fields with format `wiki`.
     52
     53=== Sample Configuration
     54
     55{{{#!ini
    4356[ticket-custom]
    4457
     
    4861test_two = text
    4962test_two.label = Another text-box
    50 test_two.value = Just a default value
     63test_two.value = Default [mailto:joe@nospam.com owner]
     64test_two.format = wiki
    5165
    5266test_three = checkbox
     
    5771test_four.label = My selectbox
    5872test_four.options = one|two|third option|four
    59 test_four.value = 2
     73test_four.value = two
    6074
    6175test_five = radio
    6276test_five.label = Radio buttons are fun
    6377test_five.options = uno|dos|tres|cuatro|cinco
    64 test_five.value = 1
     78test_five.value = dos
    6579
    6680test_six = textarea
     
    7185}}}
    7286
    73 ''Note: `select` タイプのフィールドを非必須 (optional) にしたい場合、 `フィールド名.options` オプションの先頭に `バーティカルパイプ (|)` を設定してください。''
     87'''Note''': To make entering an option for a `select` type field optional, specify a leading `|` in the `fieldname.options` option.
    7488
    75 === カスタム属性を含むレポート ===
     89=== Reports Involving Custom Fields
    7690
    77 カスタム属性を含む TracReports では比較的 SQL を間違えやすいです。 `ticket_custom` 表の `JOIN` はカスタム属性ごとにそれぞれ必要です。
     91Custom 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`.
    7892
    79 以下の例は `progress` という名前のカスタム属性を含むレポートです:
    80 {{{
    81 #!sql
     93{{{#!sql
     94SELECT p.value AS __color__,
     95   id AS ticket, summary, owner, c.value AS progress
     96  FROM ticket t, enum p, ticket_custom c
     97  WHERE status IN ('assigned') AND t.id = c.ticket AND c.name = 'progress'
     98AND p.name = t.priority AND p.type = 'priority'
     99  ORDER BY p.value
     100}}}
     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.
     103
     104However, 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:
     105{{{#!sql
    82106SELECT p.value AS __color__,
    83107   id AS ticket, summary, component, version, milestone, severity,
     
    86110   changetime AS _changetime, description AS _description,
    87111   reporter AS _reporter,
    88   (CASE WHEN c.value = '0' THEN 'None' ELSE c.value END) AS progress
     112   (CASE WHEN c.value = '0' THEN 'None' ELSE c.value END) AS progress
    89113  FROM ticket t
    90114     LEFT OUTER JOIN ticket_custom c ON (t.id = c.ticket AND c.name = 'progress')
     
    94118}}}
    95119
    96 この `LEFT OUTER JOIN` ステートメントに特に注意してください。
     120Note in particular the `LEFT OUTER JOIN` statement here.
     121
     122Note that if your config file uses an '''uppercase''' name:
     123{{{#!ini
     124[ticket-custom]
     125
     126Progress_Type = text
     127}}}
     128you would use '''lowercase''' in the SQL: `AND c.name = 'progress_type'`.
     129
     130=== Updating the database
     131
     132As noted above, any tickets created before a custom field has been defined will not have a value for that field. Here is some SQL (tested with SQLite) that you can run directly on the Trac database to set an initial value for custom ticket fields. It inserts the default value of 'None' into a custom field called 'request_source' for all tickets that have no existing value:
     133
     134{{{#!sql
     135INSERT INTO ticket_custom
     136   (ticket, name, value)
     137   SELECT
     138      id AS ticket,
     139      'request_source' AS name,
     140      'None' AS value
     141   FROM ticket
     142   WHERE id NOT IN (
     143      SELECT ticket FROM ticket_custom
     144   );
     145}}}
     146
     147If 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:
     148
     149{{{#!sql
     150INSERT INTO ticket_custom
     151   (ticket, name, value)
     152   SELECT
     153      id AS ticket,
     154      'request_source' AS name,
     155      'None' AS value
     156   FROM ticket
     157   WHERE id NOT IN (
     158      SELECT ticket FROM ticket_custom WHERE name = 'request_source'
     159   );
     160}}}
    97161
    98162----