Skip to main content

Custom fields

The Custom fields tab lets you add your own business attributes to FoxPlan, on top of the standard fields. They then appear on project, card, story, risk and decision forms and feed filters and exports.

Custom fields tab

Settings → Workspace → Custom fields

Field definition​

For each custom field, you set:

  • Label — Display text (FR / EN as needed)
  • Technical key — Internal identifier, immutable once used
  • Type — Text, Number, Boolean, Date, Single-select list, Multi-select list, Reference-data list
  • Target entity — Project, Portfolio, Card, Story, Risk, Decision, Budget, etc.
  • Required or optional
  • Visible / Editable by role (combined with User access)

List values​

For a Single-select list or Multi-select list field, click Add, then enter the key and the label of each value in every language you need. The green check mark confirms a row, but you do not have to click it:

  • Save also confirms the rows still being edited. A row added and left empty is ignored; an empty or already used key blocks the save with a message.
  • Closing the dialog (cross, Esc or Cancel) with unsaved changes asks for confirmation: Save keeps them, Discard restores the field as it was when you opened it.

"Pending" task status​

The Status system field of tasks offers an optional "Pending" (Standby) value, for a task on hold: neither to be started nor finished. Calculations treat it as "Ongoing".

It is hidden by default. To enable it: pick the Task object type, open the Status field (pencil icon), tick "Display the "Standby" value in the status list", then save.

  • Option ticked — the value appears in status lists (task panel, Gantt, timesheet) and the "Pending" column shows in the Kanban boards. Projects created before this status existed automatically get their "Pending" column, between "Open" and "Ongoing".
  • Option unticked — the value disappears from lists, and columns carrying only this status are hidden in the Kanban boards and in the project's Cards & Agility tab. They remain stored: ticking the option again brings them back. A column that still holds cards stays visible.

Committee types​

The Committee type system field offers Steering committee, Project committee, Architecture committee and Other by default. Its list of values is edited like a custom field's: choose the Committee object type, open the Committee type field (pencil icon), then add, rename or remove values in each language and save.

New values appear straight away in the committee form (Project → Committees). Keep the keys of values already in use: a committee stores its type's key, and a key removed from the list would be shown raw.

Form layout (edit groups)​

You can group fields into edit groups displayed together on the form. This helps structure complex forms (e.g. "Financial data", "Client information", "Compliance").

Best practices​

  • Choose the right type: a wrong type cannot be undone (e.g. a number stored as text won't aggregate).
  • Limit required fields: too many required fields slow input down and discourage contributors.
  • Prefix business labels to distinguish them from standard fields ("Biz_WBSCode", "Client_Ref").
  • Think exports: every custom field is exportable through the Datamart or the API.
Retroactive change

Changing the type of an already populated field does not erase existing values but may hide them. Prefer creating a new field and migrating data when needed.