Changes between Version 1 and Version 2 of TracTicketsCustomFields

Timestamp:

09/16/05 00:03:51 (20 years ago)

Author:

trac

Comment:

--

TracTicketsCustomFields

@@ -1 +1 @@
 = Custom Ticket Fields =
-Trac support adding custom, user-defined, fields to the ticket module. Using custom fields, you can add typed, site-specific, properties to tickets.
+Trac supports adding custom, user-defined fields to the ticket module. Using custom fields, you can add typed, site-specific properties to tickets.
 
 '''Note: In Trac 0.8, this feature is still experimental.'''
 
-== Configuriation ==
+== Configuration ==
 Configuring custom ticket fields is done in the TracIni config file.
 
-All field definitions should be under a section named [ticket-custom] in the ini-file.
+All field definitions should be under a section named '''{{{[ticket-custom]}}}''' in the ini-file.
 
 The syntax of each field definition is:
@@ -15 +15 @@
  ...
 }}}
-Looking at the example below should help explain the syntax.
+The example below should help to explain the syntax.
 
 === Available Field Types and Options ===
@@ -38 +38 @@
    * label: Descriptive label.
    * value: Default text.
-   * width: Width in columns.
-   * height: Height in lines.
+   * cols: Width in columns.
+   * rows: Height in lines.
    * order: Sort order placement.
 
@@ -45 +45 @@
 {{{
 [ticket-custom]
+
 test_one = text
 test_one.label = Just a text box
@@ -69 +70 @@
 test_six.label = This is a large textarea
 test_six.value = Default text
-test_six.width = 60
-test_six.height = 30
+test_six.cols = 60
+test_six.rows = 30
 }}}
 
+=== Notes ===
+Do not insert space characters between '{{{|}}}'-separated option values for ''radio'' and ''select'' fields.
+ * ok: {{{FIELD_NAME.options = un|deux|trois}}}
+ * invalid: {{{FIELD_NAME.options = un | deux | trois}}}
+
 ----
-See also: TracTickets, TracIni
+See also: TracTickets, TracIni, TracIniReportCustomFieldSample