What it does
Custom fields let you add the data your workflow needs beyond a task's built-in fields — seventeen field types from Text and Number through Dropdown, People, and Files. A field can be scoped to a single List or to an entire Space.
Who needs it
Teams whose work needs to track something IterDone doesn't ask about by default — a client's budget, a campaign's channel, a build's version number.
Why use it
Adding exactly the two or three fields you actually need, instead of adopting a fixed schema built for someone else's workflow, is the difference between a tool that fits and one you fight.
How it works
Custom fields add the data your workflow actually needs, beyond a task's built-in fields. Add one from a List's Fields panel (the grid icon in the list toolbar), which offers a Create new tab and, at the List level, an Add existing tab for reusing fields already defined elsewhere.
Every field type currently creatable:
- Text and Text area (Long Text) — a single line or a longer block.
- Number and Money.
- Date.
- Dropdown and Labels (Multi-select) — both take a comma-separated list of options when you create them, e.g. "Low, Medium, High".
- Checkbox.
- Rating.
- Progress (Manual).
- Website, Email, and Phone.
- People — pick one or more people from the workspace as the value.
- Voting.
- Location.
- Files.
A handful of other types — Formula, Relationship, Rollup, Progress (Auto), Signature, Button, and Tasks — appear in the type picker for completeness but aren't creatable yet.
A field is scoped to either a List (visible only there) or a Space (visible on every List inside it, created from the Space's own "Custom Fields" context-menu entry). The Fields panel's Add existing tab also lets you attach a field that already exists somewhere else in the workspace onto the current List — it becomes the same field with the same values everywhere it's attached, not a copy — and detach it again later without deleting it from wherever else it's still in use.