Changes between Version 40 and Version 41 of TracTicketsCustomFields
- Timestamp:
- Mar 6, 2022, 9:18:25 AM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTicketsCustomFields
v40 v41 1 1 = Custom Ticket Fields 2 2 3 Trac supports adding custom, user-defined fields to the ticket module. With custom fields you can add typed, site-specific properties to tickets. 3 4 … … 16 17 17 18 === Field Names 19 18 20 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. 19 21 … … 154 156 SELECT p.value AS __color__, 155 157 id AS ticket, summary, owner, c.value AS progress 156 157 158 AND p.name = t.priority AND p.type = 'priority'159 158 FROM ticket t, enum p, ticket_custom c 159 WHERE status IN ('assigned') AND t.id = c.ticket AND c.name = 'progress' 160 AND p.name = t.priority AND p.type = 'priority' 161 ORDER BY p.value 160 162 }}} 161 163 '''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. … … 170 172 reporter AS _reporter, 171 173 (CASE WHEN c.value = '0' THEN 'None' ELSE c.value END) AS progress 172 173 174 JOIN enum p ON p.name = t.priority AND p.type='priority'175 176 174 FROM ticket t 175 LEFT OUTER JOIN ticket_custom c ON (t.id = c.ticket AND c.name = 'progress') 176 JOIN enum p ON p.name = t.priority AND p.type = 'priority' 177 WHERE status IN ('new', 'assigned', 'reopened') 178 ORDER BY p.value, milestone, severity, time 177 179 }}} 178 180