Custom Fields — Customize Tasks

Written By Miro Flemke

Last updated About 1 month ago

What are custom fields?

Custom fields let you tailor tasks to your workflow. Create your own fields—such as “Priority,” “Department,” or “Estimated Effort”—and enter the appropriate values for each task. This way, you can capture exactly the information that’s important to your team.

Here’s how it works

  1. Go to your team’s settings.

  2. Click on Custom Fields.

  3. Click Create Field.

  4. Choose a name and the field type.

  5. Save the field—it’s now available in all of your team’s tasks.

Available field types

Text

Free-form text field for any input

"External Reference," "Note"

Dropdown

Selection from predefined values, optionally with colors

"Priority" (High, Medium, Low)

Person

Assignment of a team member

"QA Lead," "Reviewer"

Date

Date Selection

"Review Date," "External Deadline"

Color-Coded Dropdown Fields

For dropdown fields, you can assign a specific color to each value. This lets you see the status at a glance—for example, red for "Urgent," yellow for "Under Review," and green for "Approved."

You can create up to 10 options per dropdown field.

Using Fields in Tasks

Once a field is created, it automatically appears in all of your team’s tasks. Open a task and fill in the fields as needed. You can change or remove values at any time.

Permissions

All team members can view and fill out custom fields. All team members can also create, edit, and delete field definitions.

Frequently Asked Questions

How many fields can I create?

You can create up to 20 custom fields per team.

Can I also use fields for projects?

Custom fields are currently only available for tasks. For projects, use project tags instead.

What happens if I delete a field?

All saved values for this field in all tasks will also be deleted. This action cannot be undone.

Tips & Notes

  • Use color-coded dropdown fields for properties that need to be quickly identifiable at a glance.

  • Use the "Person" field to map additional roles (e.g., reviewer, QA manager) alongside the standard assignment field.

  • Keep the number of fields manageable—too many fields can make the layout cluttered.