Custom Fields

Custom Fields let you control the task information OrbitalWP stores, displays, filters, and reports on. They include built-in task fields such as Priority and Due Date, plus user-created fields for the extra details your workflow needs.

How This Fits In OrbitalWP

Custom fields appear across task editing, task templates, task details, Kanban and Timeline views, reports, and integrations that display task data. Field labels and option labels are managed from one place, so a label change can update how that field appears throughout OrbitalWP.

Where To Find It

In the WordPress admin, open Orbital and choose Custom Fields.

The page includes an Add New Field area for creating fields and an Existing Fields table for editing fields that already exist.

Before You Start

  • You need admin access to manage custom field definitions.
  • Field keys are unique identifiers. Choose them carefully because they cannot be changed after creation.
  • Changing a field label changes how the field is displayed. It does not change the field key or remove saved task values.
  • Deleting a user-created field removes that field definition and its saved custom field data.

What You Can Do

You can create user-defined fields using these field types:

  • Text Field
  • Textarea
  • Dropdown
  • Checkbox
  • Radio Buttons
  • Number
  • Email
  • URL
  • Date
  • Image Upload

OrbitalWP also includes protected built-in fields: Priority, Start Date, Due Date, Approval Status, Percent Complete, Completed, Assignee, and Closed.

Built-in fields can be edited in limited ways, such as changing labels, descriptions, locations, required settings, and option labels where available. They cannot be deleted, and their field type cannot be changed.

Basic Workflow

  1. Open Orbital and choose Custom Fields.
  2. In Add New Field, enter a Field Key and Field Label.
  3. Choose the Field Type.
  4. If the field is a Dropdown, Radio Buttons, or Checkbox field, add the available Options.
  5. Choose the Location: Sidebar or Main Content Area.
  6. Enable Required if the field must be filled in when a task is saved.
  7. Select Add Field.
  8. Open a task or task template and fill in the field where it appears.

Important Controls And Settings

Location controls where the field appears on the task edit screen. Sidebar fields appear in the Orbital sidebar under Fields. Main Content Area fields appear in the Custom Fields box.

Options are used by Dropdown, Radio Buttons, and Checkbox fields. Option labels can be changed later. Option keys are kept stable after creation so existing task values continue to match the correct option.

Required fields must have a valid value when the task is saved. Some field types also validate their format, such as Email, URL, Date, Number, and Image Upload fields.

Image Upload fields use the WordPress media library. A user must have permission to upload or choose media before they can select or change an image.

Where Fields Appear

  • Task edit screens and task templates show custom fields based on the field location.
  • Task detail views use the current field labels and show saved values when available.
  • Kanban and Timeline grouping can include option-based fields such as Dropdown, Radio Buttons, and Checkbox fields, along with supported built-in grouping fields.
  • Reports use current labels and option labels for supported built-in task fields.
  • Frontend task forms use current labels and options for supported fields included in the form.
  • If Bricks Builder integration is enabled, task custom fields can be available as Orbital dynamic data sources, subject to task read access.

What Affects What You See

Custom field visibility and editing depend on your OrbitalWP permissions, the task type, and the field being edited.

  • Users need task read access to view task field values.
  • Users need task edit access to edit most custom fields.
  • Assignee changes require assignee management access.
  • Approval Status and Closed require approval access.
  • Approval Status and Closed are parent-task workflow fields and are not shown for subtasks.
  • Approved tasks can lock completion-related fields such as Completed and Percent Complete.
  • Blank fields may be hidden in some task detail displays.

Deeper Notes

Changing a label is different from changing saved task data. For example, renaming Priority to Importance changes the display label, but existing priority values remain attached to the same field.

For option-based fields, changing an option label updates how that option is displayed. The underlying option key remains stable so saved task values continue to work.

Built-in fields are protected because other OrbitalWP features depend on them. You can adjust how they are presented, but you cannot remove them or convert them into another field type.

Common Problems

I cannot see the Custom Fields page. You need admin access to manage custom field definitions.

A field is visible but cannot be edited. You may not have permission to edit that field, or the task may be locked by an approval rule.

Assignee, Approval Status, or Closed is missing. These fields have special permission rules. Approval Status and Closed are also parent-task workflow fields, so they do not appear on subtasks.

A field is missing from Group tasks by. Grouping is intended for option-style fields and supported built-in fields. Text, textarea, email, URL, number, date, and image fields are not general Kanban grouping fields.

An option label changed but old tasks still have the same value. That is expected. The label changed, but the saved option key remains the same so existing task data stays connected.

An Image Upload field cannot be changed. The user needs permission to use the WordPress media library.

A Bricks dynamic data value shows Not Set or a permission message. The field may not have a value, the current item may not be a task, the Bricks integration may not be active, or the viewer may not have OrbitalWP task read access.