Hi, To add custom field, the ticket_custom table is in the format of.
id name value The problem with this is it makes it very difficult to write sql to display the custom fields in any report. My question is why not just create a ticket_custom table like this id customfield1 => for example, progress customfield2 => for example, estimate_hour this way, it is more easy to write sql to report custom fields and it is also more efficient. Also, would it be ok to add a custom field just to the ticket table? If we name the custom field with a prefix, it won't conflict with future ticket table. (for example, add custom_progress, custom_estimate_hour) by the way, we just started to use Trac for our a new project, so far, works great. thanks/chong _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
