IMPORTANT - Forge Framework Limitations

Transition Screens

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-322

Open

Inline Editing on Jira Issue View

Forge custom fields do not support inline editing on issue view.

FRGE-243: inline custom field editResolved

Open

Jira cloud mobile app support

Forge custom fields do not work on Jira Cloud mobile app.

FRGE-538: Forge Custom field types don't work on the Jira Cloud Mobile appNeeds Triage

Bulk Update

FRGE-648: Custom field rendered as text area on Bulk Update screenNeeds Triage

Forms

https://ecosystem.atlassian.net/browse/FRGE-1243

Release date: unknown

Issue view tabs

Calculated and Comment fields (Hardcoded fields) won´t appear on screens where the Default or Field tabs are not selected.

Issue Navigator support for images, graphics and avatars

Forge custom fields with graphics(pictures, avatars, etc.) do not work well in issue navigator and boards

https://ecosystem.atlassian.net/browse/FRGE-135

https://trello.com/c/6HuVzQqj

Jira automation not fully supported

FRGE-1108: Forge custom fields should be fully supported in AutomationGathering Interest

JWM list view

Forge custom fields do not work in JWM list view.

FRGE-1114: Support for Forge custom fields on JWM list viewGathering Interest

Other third party apps (JXL, PowerBI)

Using Forge custom fields in other apps doesn’t always work as expected. Third party integration such as JXL or PowerBI can pose issues when trying to use Forge custom fields with the app. It is currently in plan to make CFS fields compatible with other apps.

Currency and Decimal fields formatting limitations in issue navigator

Currency Fields require a custom display to showcase both the currency symbol and the numerical value. Due to this manual rendering and storage as an object with multiple properties (as opposed to a simple number), Jira does not apply its standard number formatting. Additionally, Jira Expressions, which we use to display these values, do not support complex formatting operations. As a result:

• Currency values may not reflect the user's locale-specific number formatting.

• Rounding to two decimal places is possible but will still not align with locale settings.

Decimal Fields might omit decimals when full numbers are entered.

Secure Fields in issue navigator

In the Issue Navigator (Filters → View all issues), secure fields will not function as intended due to an Atlassian limitation that ignores permissions on this screen. To maintain privacy and respect view permissions, secure fields are not displayed in the Issue Navigator. Instead, you will see "Map of 1 Element" where the secure field would normally appear. View permissions for secure fields are not supported in the Issue Navigator and can only be enforced in all other view screens.

Basic search in issue navigator

The feature to list values using Basic Search is not supported due to Atlassian limitations. However, this functionality works seamlessly when using JQL (Jira Query Language) to list values. Users who rely on Basic Search for filtering or listing values may experience issues as the feature does not support this method. This limitation is beyond our control and requires changes from Atlassian.