Hi @Paul Madison There is no official answer to this question but as Plan was not an inbuilt and was a external plugin previously so there are some limitations on the custom field types that plan was and currently supporting and this is also similar to the field types coming from the external plugins as those are also not supported with Plan.
There are some other factors that may have an impact on the plans to not support all the custom fields types.
- Performance and Scalability
- Consistency and Integrity with other Jira objects
- Functionality Alignment
This is may be updated in future when Atlassian enhanced the functionality of plan
Currently below are the supported custom fields available to use in Plans
https://support.atlassian.com/jira-software-cloud/docs/enable-custom-fields-used-in-advanced-roadmaps-in-jira/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.