Forge Jira custom fields are not available in Jira Plans (Advanced Roadmaps).

When configuring custom fields in Plans, Forge-created fields do not appear in the available fields list, regardless of data type. This prevents teams from using Forge app data for roadmap planning, prioritization, and backlog management.

This gap is particularly impactful for Forge custom fields using the "object" data type, which stores structured, multi-property data and supports dot-notation JQL queries.

 
Two Levels of Support Requested:

1. Basic Forge custom field support in Plans - Display the field's output as a read-only string value in Plans columns. This would give teams visibility into the data during planning.
2. Sub-property access for "object" type fields - Allow Plans to introspect searchAlias definitions from the Forge manifest so users can filter, sort, and group by individual properties within the object.