Custom fields let you record details that don’t have a built-in place on a task. Each field is a name and a value, both plain text.
Add a custom field
- Open the task.
- Under Custom fields, type a Field name, such as “Client” or “Budget”.
- Type a Value.
- Select Add.
The field appears as a row on that task. Select the × beside it to remove it.
Edit a value
To change a value, remove the field and add it again with the new value. Adding a field with a name that already exists replaces the earlier value.
How custom fields behave
- They belong to one task. There is no board-wide field definition, so each task decides which fields it has.
- Names and values are saved as text. Numbers and dates are not validated or formatted.
- You need permission to edit the task to add or remove fields. Anyone who can view the task can read them.
- Custom fields are not part of the filter bar and aren’t searched by the board search box.
- They are included in a task’s data when you use the REST API.
The name _reactions is reserved. KanbanWP uses it to store emoji reactions on comments, and it is hidden from the list.
Keep fields consistent
Because every field is free text, agree on names as a team. “Client” and “client name” would be two different fields. A short list of agreed names written in the board description works well.
When to use something else
- For a fixed set of categories you want to filter on, use labels.
- For ownership, use assignees.
- For progress through a process, use stages.
- For steps inside one task, use a checklist.
Custom fields suit identifiers and reference details, such as an order number, a URL or a budget figure.