Changes between Version 3 and Version 4 of TracTicketsCustomFields

Timestamp:

Jun 9, 2024, 1:47:47 PM (4 weeks ago)

Author:

trac

Comment:

--

TracTicketsCustomFields

@@ -1 +1 @@
 = Custom Ticket Fields
-
 Trac supports adding custom, user-defined fields to the ticket module. With custom fields you can add typed, site-specific properties to tickets.
 
@@ -17 +16 @@
 
 === Field Names
-
 A 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.
 
@@ -64 +62 @@
      * `reference` to treat the content as a queryable value
      * `list` to interpret the content as a list of queryable values, separated by whitespace
+   * ticketlink_query: Query for linkifying ticket values.
+     Not applicable for format `plain` and `wiki`.
  * '''checkbox''': A boolean value check box.
    * label: Descriptive label.
    * value: Default value, 0 or 1.
    * order: Sort order placement.
+   * ticketlink_query: Query for linkifying ticket values.
  * '''select''': Drop-down select box. Uses a list of values.
    * label: Descriptive label.
@@ -73 +74 @@
    * value: Default value (one of the values from options).
    * order: Sort order placement.
+   * ticketlink_query: Query for linkifying ticket values.
  * '''radio''': Radio buttons. Essentially the same as '''select'''.
    * label: Descriptive label.
@@ -78 +80 @@
    * value: Default value, one of the values from options.
    * order: Sort order placement.
+   * ticketlink_query: Query for linkifying ticket values.
  * '''textarea''': Multi-line text area.
    * label: Descriptive label.
@@ -97 +100 @@
 
 Macros will be expanded when rendering `textarea` fields with format `wiki`, but not when rendering `text` fields with format `wiki`.
+
+For applicable fields, the `ticketlink_query` option
+overrides [[TracIni#query-ticketlink_query-option|"[query] ticketlink_query"]], and the format is the same as
+that option. When the `ticketlink_query` option
+is not specified, `[query]` `ticketlink_query` is used to
+linkify the field.
 
 === Sample Configuration
@@ -156 +165 @@
 SELECT p.value AS __color__,
    id AS ticket, summary, owner, c.value AS progress
-FROM ticket t, enum p, ticket_custom c
-WHERE status IN ('assigned') AND t.id = c.ticket AND c.name = 'progress'
-  AND p.name = t.priority AND p.type = 'priority'
-ORDER BY p.value
+  FROM ticket t, enum p, ticket_custom c
+  WHERE status IN ('assigned') AND t.id = c.ticket AND c.name = 'progress'
+AND p.name = t.priority AND p.type = 'priority'
+  ORDER BY p.value
 }}}
 '''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.
@@ -172 +181 @@
    reporter AS _reporter,
    (CASE WHEN c.value = '0' THEN 'None' ELSE c.value END) AS progress
-FROM ticket t
-   LEFT OUTER JOIN ticket_custom c ON (t.id = c.ticket AND c.name = 'progress')
-   JOIN enum p ON p.name = t.priority AND p.type = 'priority'
-WHERE status IN ('new', 'assigned', 'reopened')
-ORDER BY p.value, milestone, severity, time
+  FROM ticket t
+     LEFT OUTER JOIN ticket_custom c ON (t.id = c.ticket AND c.name = 'progress')
+     JOIN enum p ON p.name = t.priority AND p.type='priority'
+  WHERE status IN ('new', 'assigned', 'reopened')
+  ORDER BY p.value, milestone, severity, time
 }}}