Custom Fields
Rule
Field definitions, per-task values, and task-card visibility are three separate
surfaces with their own actions. Use the definition actions for the schema, the
update-task fieldValues patch for values, and the visible-field actions for
what shows on cards.
Definitions
- Use
list-custom-fields,create-custom-field,update-custom-field, anddelete-custom-fieldfor field definitions. - Use
reorder-custom-fieldswith every field id in the desired order when moving fields in the Fields list. - A field's
typeis immutable after creation;update-custom-fieldpatches thetitleand/or type-compatibleconfigonly. delete-custom-fieldonly after explicit user confirmation; warn that deleting the definition removes its values on every task.
Field types and config
- Custom field types are
text,rich_text,number,percent,currency,single_select,multi_select, anddate. - Number, percent, and currency field
precisionlimits decimal places;precision: 0means whole numbers only. Number fields also support optionalpositiveOnly. - Select option colors are named tokens:
red,orange,yellow,green,blue,purple,pink, andgray.
Values on tasks
- Use
list-taskswithincludeFieldsto read per-task custom values andupdate-taskwithfieldValuesto set or clear them; empty values clear the stored row.
Task-card visibility
- Use
list-visible-task-fieldsandupdate-visible-task-fieldsto read or change which fields appear on task cards (max 3, persisted per user in SQL).
What view-screen returns
- On
/tasks,view-screenincludesvisibleTaskFieldsfrom stored prefs for the custom fields currently shown on task cards andselectedTaskFieldsfor a highlighted task. - On
/fields,view-screenreturns the field-definition list andselectedItemwhen a field is highlighted. navigation.fieldIdhighlights a custom field when the Fields page is opened from a deep link.
Related Skills
- task-inbox-workflow — reading visible task context before editing.
- store-conventions — how custom field value writes are shaped in the store.