The SQL required for TracReports to include custom ticket fields is relatively hard to get right. You need a `JOIN` with the `ticket_custom` field for every custom field that should be involved.

77

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`.

78

78

79

The following example includes a custom ticket field named `progress` in the report:

79

{{{

80

#!sql

81

SELECT p.value AS __color__,

82

id AS ticket, summary, owner, c.value AS progress

83

FROM ticket t, enum p, ticket_custom c

84

WHERE status IN ('assigned') AND t.id = c.ticket AND c.name = 'progress'

85

AND p.name = t.priority AND p.type = 'priority'

86

ORDER BY p.value

87

}}}

88

'''Note''' that this will only show tickets that have progress set in them, which 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. If that's all you want, you're set.

89

90

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.

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:

112

113

{{{

114

#!sql

115

INSERT INTO ticket_custom

116

(ticket, name, value)

117

SELECT

118

id AS ticket,

119

'request_source' AS name,

120

'None' AS value

121

FROM ticket

122

WHERE id NOT IN (

123

SELECT ticket FROM ticket_custom

124

);

125

}}}

126

127

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: