We know several limitations related to the Custom Field Suite app related to Atlassian Forge framework. |
Issue 1: Using Forge custom fields on a JSM portal or a JSM request type is impossible.
https://ecosystem.atlassian.net/browse/FRGE-778
Issue 2: Using the Forge custom field on transition screens is impossible. The fields can be assigned to the screen, but they will be rendered as text fields.
https://ecosystem.atlassian.net/browse/FRGE-630
Issue 3: Forge custom fields do not support inline editing on issue view.
https://ecosystem.atlassian.net/browse/FRGE-243
Issue 4: Forge custom fields do not work on Jira Cloud mobile app.
https://ecosystem.atlassian.net/browse/FRGE-538
Issue 5: Custom fields are rendered as free text fields on bulk update.
https://ecosystem.atlassian.net/browse/FRGE-648
Issue 6: Forge custom fields do not work in Forms.
https://ecosystem.atlassian.net/browse/FRGE-1243
Issue 7: Calculated and Comment fields (Hardcoded fields) won´t appear on screens where the Default or Field tabs are not selected.
Issue 8: It is not possible to change the custom field type.
Issue 9: The sum (Average) of numeric values in linked issues won't work with read-only fields.
Issue 10: Forge custom fields with graphics(pictures, avatars, etc.) do not work well in issue navigator and boards
https://ecosystem.atlassian.net/browse/FRGE-135
Issue 11: Forge custom fields are not supported by Jira automation of the box
https://ecosystem.atlassian.net/browse/FRGE-1108