Custom fields and templates
Two ways to make a task match your process: add the fields you need, and start new tasks already filled in.
Both need a paid plan to set up. Once set up, they keep working on any plan.
Custom fields
A custom field is attached to every task in one project. Project settings, then Custom fields, then Add field.
Fields are per project, not per workspace. A support project and an engineering project can each have the fields they need without carrying each other's.
The field types
| Type | For |
|---|---|
| Text | Anything short and free-form |
| Number | A quantity. Validated as a number |
| Checkbox | Yes or no |
| Date | A day, as YYYY-MM-DD |
| URL | A link. Has to start with http://, https:// or mailto: |
| Single select | One of a list of options you define |
Single-select options are typed as a comma-separated list, like low, med, high.
There is no person field and no multi-select. For "who", use assignees. For several values, a set of checkboxes or separate fields is the way.
Setting a value
Values live in a Custom fields section on the task, below the rest. It appears only when the project has fields, so a project without them is not cluttered with an empty heading.
A value saves when you leave the field or press Enter. Setting a value needs Member access; guests can read them but not change them.
What you can and cannot do with them
This is the part to read before you design a process around custom fields.
You cannot filter or sort tasks by a custom field. Not in list, board, table or calendar, and not in a saved view. A custom field records something on a task; it does not organise the task list. If you need to slice the board by it, use labels, which filter everywhere.
You can aggregate one. Project insights has a card for a single custom field: a number field gives you a count, a sum, an average and the p50 and p90, and other types give you a breakdown by value. That lives with Analytics, which is Pro.
Changing and deleting a field
The type can be changed only while no task has a value in it. Once values exist the type is fixed, because reinterpreting stored values as another type would silently corrupt them.
Deleting a field hides it and its stored values, as the confirmation says. The values are not destroyed, but there is no way to bring them back from the interface either. Treat a delete as final.
What it costs
Creating a field needs Starter or above. Everything else is ungated: a workspace that drops to Free keeps its fields, keeps the values, and can still edit them. Only Add field disappears.
Creating, changing and deleting a field needs admin on the project or the workspace.
Task templates
A template pre-fills a new task. Project settings, then Templates.
A template holds:
- A name, which becomes the task's title when the title is still empty.
- A description, as HTML. There is no visual editor for this one, so it is for text you prepare once.
- A default priority, state, labels and assignees.
Workspace-wide or one project
Choose the scope when you create it:
- Workspace-wide templates appear in every project.
- Project-scoped templates appear only in the project you made them in.
The scope is set at creation and cannot be changed later. If you need to move one, make it again at the right scope.
Using one
In the create-task dialog, pick from Use template. Each option says whether it is a project or a workspace template. The form fills in, and you can change anything before creating the task. Nothing is locked.
What it costs
Creating a template needs Starter or above. Existing templates keep working and keep applying after a downgrade; only New template goes away.
A workspace-wide template needs a workspace admin. A project-scoped one can be managed by an admin of that project.
Troubleshooting
| What you see | What it means |
|---|---|
| "Custom fields require a paid plan." | Creating fields needs Starter. Existing fields and values stay editable on Free. |
| "Templates require a paid plan." | The same, for templates. |
| "Admin access required" | Fields and templates are configured by admins. Members fill them in. |
| "Cannot change type once values exist" | Some task already has a value. Create a new field instead. |
| "Value is not a valid option" | A single-select value is not in the option list. |
| "URL must start with http://, https://, or mailto:" | A bare domain is not accepted. |
| "Date must be in YYYY-MM-DD format" | Use the full date format. |
| "Not a valid number" | A number field will not take text. |
| No Custom fields section on a task | The project has no fields yet. |
| You cannot filter by your field | Filtering and sorting by custom fields does not exist. Use labels for that. |
| A template's labels did not appear | Check you applied it in the create-task dialog. A template applied by a recurring schedule carries only the name, description and priority. |