Changes between Version 3 and Version 4 of TracTicketsCustomFields

Timestamp:

Mar 16, 2019, 5:26:46 PM (6 years ago)

Author:

trac

Comment:

--

TracTicketsCustomFields

@@ -18 +18 @@
    * value: Default value.
    * order: Sort order placement. (Determines relative placement in forms with respect to other custom fields.)
-   * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting. (''since 0.11.3'')
+   * format: One of: 
+     * `plain` for plain text 
+     * `wiki` to interpret the content as WikiFormatting (''since 0.11.3'') 
+     * `reference` to treat the content as a queryable value (''since 1.0'') 
+     * `list` to interpret the content as a list of queryable values, separated by whitespace (''since 1.0'')
  * '''checkbox''': A boolean value check box.
    * label: Descriptive label.
@@ -36 +40 @@
    * label: Descriptive label.
    * value: Default text.
-   * cols: Width in columns.
+   * cols: Width in columns
    * rows: Height in lines.
    * order: Sort order placement.
    * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting. (''since 0.11.3'')
+
+Macros will be expanded when rendering `textarea` fields with format `wiki`, but not when rendering `text` fields with format `wiki`.
 
 === Sample Config ===
@@ -110 +116 @@
 Note in particular the `LEFT OUTER JOIN` statement here.
 
+Note that if your config file uses an uppercase name, e.g.,
+{{{
+[ticket-custom]
+
+Progress_Type = text
+}}}
+you would use lowercase in the SQL:  `AND c.name = 'progress_type'`
+
 === Updating the database ===