1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
|
= 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.
== Configuration
Configuring custom ticket fields is done in the [wiki:TracIni trac.ini] file. All field definitions should be under a section named `[ticket-custom]`.
The syntax of each field definition is:
{{{
FIELD_NAME = TYPE
(FIELD_NAME.OPTION = VALUE)
...
}}}
The example below should help to explain the syntax.
=== Available Field Types and Options
* '''text''': A simple (one line) text field.
* label: Descriptive label.
* value: Default value.
* order: Sort order placement; this determines relative placement in forms with respect to other custom fields.
* format: One of:
* `plain` for plain text
* `wiki` to interpret the content as WikiFormatting
* `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.
* value: Default value, 0 or 1.
* order: Sort order placement.
* '''select''': Drop-down select box. Uses a list of values.
* label: Descriptive label.
* options: List of values, separated by '''|''' (vertical pipe).
* value: Default value (one of the values from options).
* order: Sort order placement.
* '''radio''': Radio buttons. Essentially the same as '''select'''.
* label: Descriptive label.
* options: List of values, separated by '''|''' (vertical pipe).
* value: Default value, one of the values from options.
* order: Sort order placement.
* '''textarea''': Multi-line text area.
* label: Descriptive label.
* value: Default text.
* cols: Width in columns. //(Removed in 1.1.2)//
* rows: Height in lines.
* order: Sort order placement.
* format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting.
* '''time''': Date and time picker. (''Since 1.1.1.'')
* label: Descriptive label.
* value: Default date.
* order: Sort order placement.
* format: One of:
* `relative` for relative dates.
* `date` for absolute dates.
* `datetime` for absolute date and time values.
If the `label` is not specified, it will be created by capitalizing the custom field name and replacing underscores with whitespaces.
Macros will be expanded when rendering `textarea` fields with format `wiki`, but not when rendering `text` fields with format `wiki`.
=== Sample Config
{{{
[ticket-custom]
test_one = text
test_one.label = Just a text box
test_two = text
test_two.label = Another text-box
test_two.value = Default [mailto:joe@nospam.com owner]
test_two.format = wiki
test_three = checkbox
test_three.label = Some checkbox
test_three.value = 1
test_four = select
test_four.label = My selectbox
test_four.options = one|two|third option|four
test_four.value = two
test_five = radio
test_five.label = Radio buttons are fun
test_five.options = uno|dos|tres|cuatro|cinco
test_five.value = dos
test_six = textarea
test_six.label = This is a large textarea
test_six.value = Default text
test_six.cols = 60
test_six.rows = 30
test_seven = time
test_seven.label = A relative date
test_seven.format = relative
test_seven.value = now
test_eight = time
test_eight.label = An absolute date
test_eight.format = date
test_eight.value = yesterday
test_nine = time
test_nine.label = A date and time
test_nine.format = datetime
test_nine.value = in 2 hours
}}}
'''Note''': To make a `select` type field optional, specify a leading `|` in the `fieldname.options` option.
=== Reports Involving Custom Fields
Custom 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`.
{{{
#!sql
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
}}}
'''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.
However, 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:
{{{
#!sql
SELECT p.value AS __color__,
id AS ticket, summary, component, version, milestone, severity,
(CASE status WHEN 'assigned' THEN owner||' *' ELSE owner END) AS owner,
time AS created,
changetime AS _changetime, description AS _description,
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
}}}
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
As noted above, any tickets created before a custom field has been defined will not have a value for that field. Here's a bit of SQL (tested with SQLite) that you can run directly on the Trac database to set an initial value for custom ticket fields. Inserts the default value of 'None' into a custom field called 'request_source' for all tickets that have no existing value:
{{{
#!sql
INSERT INTO ticket_custom
(ticket, name, value)
SELECT
id AS ticket,
'request_source' AS name,
'None' AS value
FROM ticket
WHERE id NOT IN (
SELECT ticket FROM ticket_custom
);
}}}
If 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:
{{{
#!sql
INSERT INTO ticket_custom
(ticket, name, value)
SELECT
id AS ticket,
'request_source' AS name,
'None' AS value
FROM ticket
WHERE id NOT IN (
SELECT ticket FROM ticket_custom WHERE name = 'request_source'
);
}}}
----
See also: TracTickets, TracIni
|
