Edgewall Software

Changes between Version 16 and Version 17 of TracTicketsCustomFields


Ignore:
Timestamp:
Nov 16, 2006, 11:46:00 PM (16 years ago)
Author:
Tim Hatch <trac@…>
Comment:

Fixing docs about ticket_custom for #4197

Legend:

Unmodified
Added
Removed
Modified
  • TracTicketsCustomFields

    v16 v17  
    7575=== Reports Involving Custom Fields ===
    7676
    77 Custom ticket fields are stored in the `custom_ticket` 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`.
     77Custom 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`.
    7878
    7979{{{
     
    8181SELECT p.value AS __color__,
    8282   id AS ticket, summary, owner, c.value AS progress
    83   FROM ticket t, enum p, custom_ticket c
     83  FROM ticket t, enum p, ticket_custom c
    8484  WHERE status IN ('assigned') AND t.id = c.ticket AND c.name = 'progress'
    8585AND p.name = t.priority AND p.type = 'priority'