Change the workflow in place
Statuses are edited where you work. Rename a stage, recolour it, move it to another category, or give one Folder its own set when the team's process changes.
Custom fields and statuses
A workflow that fits the work, not a fixed set of states.
Name your own statuses, cap work in progress, add the fields your team actually tracks, and mark what is waiting on what. Statuses and custom fields are set per Space, Folder or List, so each team shapes its own board without changing anyone else's.
Custom task statuses per list
Statuses are named, coloured stages grouped into Not Started, Active, Done and Closed. Define them once on a Space, then let each Folder or List inherit that set or break off with its own. Rename a status, recolour it, drag it into a new order, and put a WIP limit on any stage so a column cannot quietly fill up. Save a set as a status template and reuse it on the next project.
Editing a List's statuses, including a WIP limit on one stage.
Custom fields for tasks
Add the data your workflow needs beyond a task's built-in properties: a client budget, a campaign channel, a build version. There are more than twenty field types, from text, number, money, date, dropdown and labels to people, rating, formula, rollup and relationship fields. A field belongs to one List or to a whole Space, and the same field can be attached to several Lists so the values stay in one place.
Adding a custom field from a List's Fields panel.
Dependencies between tasks
Mark a task as waiting on another, or as blocking one. The dependency shows on the task itself and as an arrow on the Gantt and timeline views, and task lists can be filtered to what is blocked or blocking. Combined with your own statuses, you can see what is stuck and why without a meeting.
Dependency arrows between blocked tasks on the Gantt view.
How it works
Shaped by the team that uses it.
Scope matters
A Space-level status set or custom field applies to everything inside it. A List-level one stays on that List, so the sprint list and the client-intake list do not have to agree.
The same from code
The REST API and the MCP server read and write the same statuses and fields the app does (create_status, update_status, reorder_statuses, list_custom_fields, set_custom_field), so a script or an AI agent can shape the workflow too.
Common questions
What people ask first.
Can I add my own workflow states?
Yes. Add, rename, recolour and reorder statuses on a Space, Folder or List, and move them between the Not Started, Active, Done and Closed categories.
Can a single list have a different workflow from the rest of the Space?
Yes. A List or Folder can inherit its parent's statuses or switch to its own set, and the change does not touch any other List.
Can I limit how much work sits in one status?
Yes. Set a WIP limit on any status. The board column shows when it is over the cap.
What custom field types are there?
More than twenty, including text, number, money, date, dropdown, labels, checkbox, rating, people, formula, rollup, relationship, signature and button fields.
Can a custom field be shared across lists?
Yes. Create it on a Space to cover every List inside it, or attach an existing field to another List. It is the same field with the same values, not a copy.
Does it support task dependencies?
Yes. A task can be marked as waiting on, or blocking, another task, and the Gantt and timeline views draw the arrows between them.
Can I set up statuses and fields through the API?
Yes. The REST API and the built-in MCP server expose status and custom field operations, so workflow setup can be scripted or handed to an agent.
Keep exploring