TicketCustomFields
TicketCustomFields routes manage ticket custom field DEFINITIONS for dashboard Ticket Settings step 5 (Ticket Custom Filed). Values on a ticket are stored separately via Ticket.Add / Ticket.Edit using each field name key (a-...).
Definitions Vs Values
- List/Get/Add/Edit/Delete change the schema in user_detail.ticket_extra_fields (settings UI).
- Ticket values use the returned name (a-1731562297) as a POST key on Ticket.Add / Ticket.Edit / Ticket.Update.
- Groups use type=group, name ga-..., and nested group_data. EditGroup updates group labels.
Field Types
- Common types: text, tel, email, number, radio, radio_custom, checkbox, select, textarea (and date when already present in saved JSON).
- select / radio / checkbox need their option arrays as documented on TicketCustomFields.Add.
- Dependencies use dependency_ticket + dependency_field_ticket + dependency_field_value_ticket. Use TicketCustomFields.Dependencies for dependency dropdown options.
Permissions
- List/Get are available to authenticated staff.
- Add/Edit/Delete/EditGroup require owner or member-admin (same as dashboard settings).
Common Flow
- Call TicketCustomFields.List to build the settings table.
- Call TicketCustomFields.Add or Edit to save a field; store the returned name key.
- On create/edit ticket screens, load definitions then send a-{id}=value with Ticket.Add / Ticket.Edit.
- Use TicketCustomFields.Dependencies when building dependency pickers.