17 | | || `component` || Values that can be used in a ticket's "component" field. The `owner` column is used as the default assignee for new tickets, if not overridden at the time of ticket submission. || |
18 | | || `enum` || Maps integer IDs for issues' priorities, severities, etc. to human-readable names. || |
19 | | || `milestone` || Project milestones. || |
| 17 | || [./TicketSystem#Tablecomponent component] || Values that can be used in a ticket's "component" field. The `owner` column is used as the default assignee for new tickets, if not overridden at the time of ticket submission. || |
| 18 | || [./TicketSystem#Tableenum enum] || Maps integer IDs for issues' priorities, severities, etc. to human-readable names. || |
| 19 | || [./TicketSystem#Tablemilestone milestone] || Project milestones. || |
28 | | || `ticket` || Tickets. || |
29 | | || `ticket_change` || Changes to tickets, on a field-by-field basis. The field value `comment` is special: it associates a comment with a set of field changes. || |
30 | | || `ticket_custom` || The values of custom ticket fields. || |
31 | | || `version` || As in `component` and `milestone`, this holds the options of the drop-down `version` list on the ticket form. Every version can have a `time` set, although that is not presently used other than for ordering the list of versions in the UI. || |
| 28 | || [./TicketSystem#Tableticket ticket] || Tickets. || |
| 29 | || [./TicketSystem#Tableticket_change ticket_change] || Changes to tickets, on a field-by-field basis. The field value `comment` is special: it associates a comment with a set of field changes. || |
| 30 | || [./TicketSystem#Tableticket_custom ticket_custom] || The values of custom ticket fields. || |
| 31 | || [./TicketSystem#Tableversion version] || As in `component` and `milestone`, this holds the options of the drop-down `version` list on the ticket form. Every version can have a `time` set, although that is not presently used other than for ordering the list of versions in the UI. || |