Custom fields and project fields

Every task has a title, dates, priority, progress and assignee. An organization can add more fields in two places:

• Form questions: each question is a field, and the requests created by the form fill it in.
• Project fields: a project can have fields that its tasks fill in. Example: Channel (choice) and Budget (amount) on every task of a marketing project. You define them from the project menu (⋯ → Project fields).

Types

Every field is a ready-made type that validates the value on its own: short and long text, email, phone, web address, whole number, decimal, amount with currency, date, time, date and time, period, single choice, multiple choice, checkbox, person, name, attachment. An email field rejects anything that is not an address; you do not have to write rules.

How project fields behave

• Only the project's work items (tasks, milestones, approvals, notes) fill them in; phases, forms, the project itself and requests do not.
• You fill them in on the task's page, in the Project fields section. They are never required.
• The project's List view shows them as columns and filters by them. The Board stays grouped by status.
• A field that has values is hidden, not deleted.
• A task with values in project fields cannot be moved to another project until you clear them.
• Not available on a project: attachment and name.

Automatic actions on fields

A project automatic action can react to a project field or to a question in its forms ("when Confidence becomes Off track → high priority"), and can write a field.

The assistant and fields

The assistant reads field values when it looks at a task, but does not write them and does not fill in forms: a person does that on the task's page.

Plan

Project fields require a plan that includes them. Without one, the values stay saved but are neither shown nor written, and they come back when the plan includes them again.