Define custom columns per project text, number, date, boolean, select, URL, email. Filter and sort by custom field values with full display across all task views.
Define the fields your project actually needs. Set values task by task. Filter, sort, and see them everywhere no configuration beyond the initial setup.
Define
Custom fields are defined per project from a type menu. Name the field, choose its type, and it becomes a column across every task in that project immediately visible in List view, editable in task detail, and available for filtering and sorting. The same seven types cover engineering, product, design, and operations workflows without any field type workarounds.
Filter & Sort
Once custom fields have values, they become full filter and sort criteria exactly like built in fields. Combine custom field filters with standard filters (status, assignee, priority) using AND logic. Sort ascending or descending on any field type. The result count updates as filters are applied so you always know how many tasks match before you commit.
Display
Custom fields aren't hidden away in the task detail panel. They render as visible columns and card data across every TARO view List, Kanban, Calendar, Gantt, Bug Tracker, and Custom tabs. In List view they appear as sortable table columns. In Kanban they appear on card previews for the fields most relevant to board context. Wherever the task appears, its custom field values travel with it.
Edit
Custom field values are editable inline from any view click a List view cell and type, toggle a boolean directly on the Kanban card, pick a select option from a dropdown that appears in place. No one needs to open the full task detail panel to update a story point estimate or flip a review toggle. The field is where you see it. The edit is where you need it.
Every project has data that matters to it specifically. Story points for engineering. Severity for QA. Client name for account management. Custom fields make TARO fit the project not the other way around.
Text, number, date, boolean, select, URL, and email handle every kind of project specific information from story points to environment flags to client contact addresses without workarounds or type coercion.
Custom fields are full first class filter criteria. "Show me all Production tasks with Story Points above 8 that haven't been reviewed" is a filter combination not a spreadsheet export and a manual scan.
Number fields sort numerically, not lexicographically. Story Points 13 ranks above Story Points 8. Date fields sort chronologically. Select fields sort alphabetically. Every type sorts the way you'd expect it to.
Custom fields don't hide. They appear as columns in List, as card data in Kanban, as sidebar columns in Gantt, as date indicators in Calendar. The data your team cares about is visible wherever they're working no separate click required.
The harder it is to update a field, the less reliably it gets updated. Inline editing from any view removes the friction entirely click the cell, change the value, move on. Fields stay accurate because updating them costs nothing.
A Story Points field in the Payments project doesn't appear in the Marketing project. Fields are defined per project so each team sees only what's relevant to their work no shared field schema cluttering every project in the workspace..
Text, number, date, boolean, select, URL, and email handle every kind of project specific information from story points to environment flags to client contact addresses without workarounds or type coercion.
Custom fields are full first class filter criteria. "Show me all Production tasks with Story Points above 8 that haven't been reviewed" is a filter combination not a spreadsheet export and a manual scan.
Number fields sort numerically, not lexicographically. Story Points 13 ranks above Story Points 8. Date fields sort chronologically. Select fields sort alphabetically. Every type sorts the way you'd expect it to.
Custom fields don't hide. They appear as columns in List, as card data in Kanban, as sidebar columns in Gantt, as date indicators in Calendar. The data your team cares about is visible wherever they're working no separate click required.
The harder it is to update a field, the less reliably it gets updated. Inline editing from any view removes the friction entirely click the cell, change the value, move on. Fields stay accurate because updating them costs nothing.
A Story Points field in the Payments project doesn't appear in the Marketing project. Fields are defined per project so each team sees only what's relevant to their work no shared field schema cluttering every project in the workspace..
Create a custom field in 10 seconds. It appears across every task and every view immediately.
Engineering teams tracking story points and environments, QA teams flagging severity and reproducibility, and ops teams logging client data all define custom fields that make TARO fit how they actually work.
800+
product teams already using TARO
Custom field types
Fields per project
Views that display fields
Click to edit inline
Engineering teams add three custom fields to every sprint project: Story Points (number), Environment (select: Dev/Staging/Prod), and PR Link (URL). Sprint planning filters by story points to balance commitment. The Kanban board shows Environment on each card so the team knows at a glance what's live versus what's still in staging. The PR link is one click from the task detail no copy pasting between tools.
Once your tasks carry the right data, TARO's views and intelligence make that data work for your team across the full delivery lifecycle.
The full task layer rich text, 7 statuses, 4 priorities, subtasks, dependencies, time tracking, and 6 view modes that custom fields extend with your project specific data.
Save any filter + sort combination as a named tab including custom field filters. "Unreviewed Prod bugs above P1" becomes a tab your whole team can open in one click.
Configurable columns with card previews that show up to 3 custom fields alongside priority and assignee so the board tells the whole story without anyone opening a task.
Story points stored as a custom number field feed directly into sprint velocity calculations and capacity planning so your agile metrics come from the same field your team edits.
The full task layer rich text, 7 statuses, 4 priorities, subtasks, dependencies, time tracking, and 6 view modes that custom fields extend with your project specific data.
Save any filter + sort combination as a named tab including custom field filters. "Unreviewed Prod bugs above P1" becomes a tab your whole team can open in one click.
Configurable columns with card previews that show up to 3 custom fields alongside priority and assignee so the board tells the whole story without anyone opening a task.
Story points stored as a custom number field feed directly into sprint velocity calculations and capacity planning so your agile metrics come from the same field your team edits.
Common questions from engineering leads, QA teams, and project managers evaluating TARO's custom field system.
When you create a Select field, you define the option list the set of values team members can choose from. Each option has a name and an optional colour. Options appear as a dropdown when a team member edits a select field on any task. In List view, select values display as colour coded pills. On Kanban cards, the select value appears alongside priority. Options can be added, renamed, or reordered by project owners at any time changes to option names propagate to all tasks that had that value set. Deleting an option prompts you to either clear the value on all tasks that had it or replace it with another option, preventing orphaned data.
Add the columns your project actually needs. Filter, sort, and see them everywhere.