Custom fields

Add your own fields to work items — a client name, a risk rating, a go-live date — when the built-in fields do not cover how your team actually works.

Plan: Pro and above

What you can do

Define fields per project: text, number, date, checkbox or single-select.
Give a select field its own list of options.
Mark a field as required.
Set and edit field values on any work item from its detail view.
Delete a field when it has served its purpose.

Getting started

Define a field

Go to Workspace settings → Projects → your project → Custom Fields.
Click + Add Field.
Fill in the form:
- Field Name — for example Story Points, Client, Go-live.
- Field Type — one of:
  
  Type What you get on the work item
  Text A free-text box
  Number A numeric box; non-numeric values are rejected on save
  Date A date picker
  Checkbox An on/off toggle
  Select A dropdown of the options you define
- Options (comma-separated) — only appears when the type is Select. Enter e.g. Low, Medium, High.
- Required field — tick to mark the field as required.
Click Save.

Type	What you get on the work item
Text	A free-text box
Number	A numeric box; non-numeric values are rejected on save
Date	A date picker
Checkbox	An on/off toggle
Select	A dropdown of the options you define

The field appears in the list below, with its type as a badge and a Required marker if you set one.

📷 Screenshot: The project Custom Fields settings page listing defined fields with their type badges.

Set a value on a work item

Open any work item in that project.
In the action bar, click Fields.
The modal loads every field defined for the project, with the right input for each type and this item's current value already filled in.
Change what you need and click Save.

Only the fields you actually changed are written back, so two people editing different fields on the same item will not overwrite each other.

📷 Screenshot: The Fields modal on a work item, showing one input per defined custom field.

If the project has no fields yet, the modal says so and links straight to the settings page where you can define them.

Deleting a field

On the settings page, click Delete on the field's row. This removes the field and every value stored against it on every work item in the project. There is no confirmation prompt and no undo — check first.

Tips

Name fields for what they hold, not for who asked for them. Client outlives Field for Dana's report.
Prefer Select over Text wherever the answer comes from a fixed list. Free text drifts (high, High, HIGH) and becomes useless the moment you want to count anything.
Keep the list short. Every field you define shows up in every work item's Fields modal, whether or not it applies.

Limits & good to know

Fields are per project. Defining Client in one project does not create it anywhere else — you define it again in each project that needs it.
A field cannot be edited once created. Renaming it, changing its type, or changing a select field's options all mean deleting it (losing the stored values) and creating it again. Add options carefully the first time.
Required is a label, not a rule. The field is marked with a red asterisk in the Fields modal, but nothing blocks you from saving a work item without it, and nothing blocks item creation.
Values live in the Fields modal only. They do not appear on cards, in list or board views, and you cannot filter, group or sort by them.
Custom-field values are not included in the Reports pages or in CSV exports.
Numbers are validated on save; every other type is stored as text exactly as you typed it.