Skip to content
WorksBuddy
TARO iconTARO
Custom Fields

Custom Fields Built for
Every Team Workflow

Define custom columns per project: text, number, date, boolean, select, URL, email. Filter and sort by their values.

Add Your First FieldSee how it works
Custom Fields
How it works

From a project with generic fields to one that fits your workflow exactly

Define the fields your project needs. Set values task by task. Filter, sort, and see them everywhere.

1

Define

Seven types. Every kind of project data covered.

Custom fields are defined per project. Name the field and choose its type, and it becomes a column on every task: visible in List view, available for filtering and sorting. Seven types cover most needs.

2

Filter & Sort

Filter and sort by any custom field in any combination.

Once they have values, custom fields become full filter and sort criteria. Combine them with standard filters using AND logic, and sort on any type. The result count updates as filters apply.

3

Display

Custom fields follow tasks into every view mode.

Custom fields aren't buried in the task detail panel. They render across every TARO view: List, Kanban, Calendar, Gantt, Bug Tracker, and Custom tabs. They're sortable in List and shown on Kanban cards.

4

Edit

Click any cell. Edit the value. No task panel required.

Custom field values are editable inline: click a List cell and type, toggle a boolean on a Kanban card, pick a select option in place. No one opens task detail just to update a story point or flip a toggle.

  • Click cell to edit inline
  • Select dropdown in place
  • Boolean toggle on card
  • AI score applied
  • Live table update
Why Custom Fields

Six reasons teams never go back

Every project has data that matters to it. Story points for engineering, severity for QA. Custom fields make TARO fit.

Who uses it
Deepak MehrotraDeepak MehrotraDeepak MehrotraDeepak Mehrotra

800+

product teams already using TARO

Built for every team whose tasks
carry more than a title and a due date

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.

7

Custom field types

50+

Fields per project

6

Views that display fields

1

Click to edit inline

Engineering Teams

Story points, environment, and PR link live on every task not in Jira.

Teams add three custom fields per sprint project: Story Points, Environment (Dev/Staging/Prod), and PR Link. Planning filters by points, and the PR is one click away.

More from TARO

Custom fields power the views. These features power the workflow.

Once your tasks carry the right data, TARO's views and intelligence make it work for your team.

Task Management

The full task layer: rich text, 7 statuses, 4 priorities, subtasks, dependencies, time tracking, and 6 view modes that custom fields extend with your data.

Custom Tabs

Save any filter as a named tab, including custom field filters. "Unreviewed Prod bugs above P1" becomes a one-click tab.

Kanban Board

Configurable columns with card previews showing up to 3 custom fields alongside priority and assignee, so the board tells the story.

Sprint & Agile

Story points stored as a custom number field feed directly into sprint velocity and capacity planning.

Questions & answers

Everything you need to know about Custom Fields

Common questions from engineering leads, QA teams, and PMs evaluating TARO's custom field system.

Custom fields are created in the project settings panel under the Fields tab. Click "Add field," enter the name, select one of the seven types, and click Save. The field immediately appears as a column in List view and in the task detail panel for all tasks in that project. Project owners and contributors can add fields; viewers cannot. There's no limit on field count. Fields take effect immediately: existing tasks start empty, and you can bulk-fill values using multi-select edit in List view.
Yes, all seven types are filterable and sortable, with type-appropriate operators. Text: is, contains, starts with, is empty; number: equals, greater than, less than, is between; date: is, is before, is after, within the last N days; boolean: is true, is false; select: is, is not, is any of; URL and email: is, contains. Custom field filters combine with built-in filters using AND logic, and sort is type-aware.
When you create a Select field, you define its options, each with a name and optional colour. In List view, select values display as colour-coded pills; on Kanban cards, the value appears alongside priority. Project owners can add, rename, or reorder options at any time, and name changes propagate to all tasks. Deleting an option prompts you to clear or replace the value on affected tasks, preventing orphaned data.
Custom fields are visible in all six task views, adapted to each. In List view, each field is a sortable column you can show or hide per view. In Kanban, you configure up to 3 fields on task cards. In Gantt, fields appear as sidebar columns beside the timeline. In Calendar, date-type fields appear as secondary date indicators. In Bug Tracker, bug-relevant fields appear automatically.
Yes to both. Field order is configurable in project settings: drag fields to set the List view column order. Each view also independently reorders which fields are visible. Deleting a field removes it from all tasks and views permanently. TARO prompts and shows how many tasks have a non-empty value before deletion. Deleted fields and values cannot be recovered, flagged clearly so deletion is intentional.
Yes, all seven custom field types support bulk editing in List view. Multi-select tasks using the checkbox column, then click Edit fields in the bulk action bar to set a value across all selected tasks at once: Story Points to 5 on 15 tasks, or Reviewed to Yes on every completed task. Each operation is logged individually in every task's activity history, so the change is auditable per task.