Skip to main content
A field is a custom field that tickets carry, such as a browser or an order number. For fields and response details, see the API reference. To set a ticket’s value for a field, pass --field Name=Value to tickets create or tickets update.

List fields

This command lists the workspace’s custom ticket fields in display order. Use this when you want to see which fields exist and find a field’s ID. --state narrows the list to active or inactive fields.
Sample output (--json)

Show a field

This command shows one field with its type, state, required flags, and dropdown options. Use this when you need the option IDs before you rename or remove an option. The record sits under a field key in data.
Required arguments:
  • <id> - Field UUID

Create a field

This command creates a custom ticket field. Use this when tickets need a new piece of structured information. --kind is one of text, textarea, integer, decimal, date, checkbox, single_option, or multi_option, and cannot be changed later. Dropdown kinds (single_option and multi_option) need at least one --option; repeat the flag for more.
The new field comes back under a field key in data.

Update a field

This command changes a field’s name, state, required flags, display order, or placeholder, and adds, renames, or removes dropdown options. Use this when a field needs adjusting. Pass only the flags you want to change. To delete a field later, first set it to inactive with --state inactive. The updated field comes back under a field key in data.
Required arguments:
  • <id> - Field UUID
--rename-option takes id=Label, where the ID is the option’s ID from fields show. The last option of a dropdown field cannot be removed.

Delete a field

This command deletes a custom ticket field along with the values tickets hold for it. Use this when a field is no longer needed. The field must be inactive first, so set it with fields update <id> --state inactive.
Required arguments:
  • <id> - Field UUID