Custom roadmap fields should be available to select for displayed records

What is the challenge?

• In custom roadmaps, fields on included records may be unavailable to select unless the records’ workspace(s) and/or workspace line(s) are also added to the workspace filter.

• This creates inconsistent behavior: records can appear on the roadmap while their custom fields cannot be selected to display on the roadmap.

What is the impact?

• Teams must expand workspace filtering solely to expose fields, which can introduce unwanted records into the roadmap.

• The configuration is confusing and adds unnecessary setup for cross-workspace roadmaps.

Describe your idea.

• Make custom fields available when their associated records are already included in a custom roadmap, regardless of whether the records’ workspace lines are explicitly selected in the workspace filter.

• Clearly align record visibility and field availability when configuring custom roadmaps.