Task custom fields

Task custom fields let each project define extra task properties beyond the standard title, description, assignees, labels, and deadline.

Examples:

  • Customer-specific rollout dates
  • Internal severity or impact scores
  • Approval flags
  • Project-specific dropdowns such as region, channel, or environment

Where to configure them

Open the project settings in the app and switch to the Task custom fields tab.

Only users on a paid seat can create new field definitions in project settings. Free-seat users can still fill existing custom fields on tasks and can keep editing or removing fields that already exist after someone with a Starter or Pro seat set them up.

Each project can have up to 10 task custom fields.

From there you can:

  • add new fields
  • change the title and description
  • choose the field type
  • mark a field as required
  • add options for single-select and multi-select fields
  • archive or delete old fields
  • rely on automatic saving while you edit

Deleting a field is destructive. It also removes the stored values of that field from tasks in the same project.

Archiving is different from deleting:

  • archived fields stay configured on the project
  • existing values stay on older tasks
  • archived fields are hidden from normal task editing
  • archived required fields stop blocking new task creation

If a project does not have any custom fields yet, the settings page shows a centered empty state with a create button and a short explanation of where these fields appear in the app.

Supported field types

  • Text
  • Number
  • Email
  • Date
  • File
  • Boolean
  • Single select
  • Multi select

Required fields

Required task custom fields are enforced when a new task is created.

If you add a new required field later, old tasks are not forced to backfill it immediately. They can still be edited normally until someone changes the custom-field values.

In the task popup

The app shows active task custom fields directly inside the task popup.

  • descriptions appear inline below the field
  • required fields show validation before save
  • single-select fields use dropdowns
  • multi-select fields use checkbox lists
  • the popup draft keeps custom field values if you close or reload the tab before saving
  • if a field definition changes while the popup is still open, incompatible draft values are cleared automatically instead of crashing the popup

In the table view and exports

Task custom fields can also be used outside the task popup:

  • enable them as extra columns in the table view
  • filter tasks by custom field values
  • include them in CSV exports

Custom-field columns are hidden by default, so projects can keep the table compact until the extra data is needed.

In Discord

The Discord bot supports required task custom fields during /task create and editable task custom fields through /task fields.

Supported in Discord:

  • Text
  • Number
  • Email
  • Date
  • Boolean
  • Single select
  • Multi select

File fields in Discord

Required file fields cannot be completed in Discord.

If a project has a required file custom field, the bot stops the flow and tells you to finish the task in the app instead. Optional file fields are shown in task info, but they are not editable from Discord.