member badge
Andrew Naisawald
Teams need stronger governance for dropdown and multi-select custom fields. Users should be able to select existing custom field values on projects and action cards, but not freely create new dropdown options unless they have permission.
Current concern:
  • Users can add new dropdown values when filling out custom fields.
  • This can create duplicate or inconsistent reporting values.
  • For example, teams could create slightly different versions of Business Unit, Sub-Business Unit, Functional Area, or Sub-Functional Area values.
  • This creates dashboard and Portfolio reporting issues because similar work may be split across inconsistent field values.
Requested outcome:
  • Workspace admins, or designated field owners, should be able to control who can add, edit, or delete dropdown options for custom fields.
  • Regular users should still be able to select from existing approved values.
  • Permissions for managing dropdown values should be separate from permissions for filling out the field on a project or action card.
Use case:
Teams using dashboards and reporting views across projects and action cards need consistent field values so leaders can accurately report by categories like Business Unit, Sub-Business Unit, Functional Area, and Sub-Functional Area without manual cleanup.
Business impact:
  • Improves reporting accuracy.
  • Reduces duplicate or messy custom field values.
  • Helps larger teams maintain governance as usage expands.
  • Supports broader rollout of dashboards, Portfolio views, and custom fields.
Suggested product behavior:
  • Add a setting on dropdown or multi-select custom fields: "Only admins / selected users can manage field options."
  • Users without permission can select values but cannot add new ones.
  • Admins or field owners can add, rename, merge, archive, or delete options.