...
| Info |
|---|
Integration with Confluence macros, PowerBI, JXL, and other third-party apps is very limited, if not impossible |
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
...
. |
| Tip |
|---|
Please vote and add comments on the linked support tickets. It is important to show Atlassian decision-makers the value of the missing features. |
...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Jira cloud mobile app support
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.
...
Bulk Update
https://ecosystem.atlassian.net/browse/FRGE-648Issue 6: Forge custom fields do not work in Forms.
...
Forms
https://ecosystem.atlassian.net/browse/FRGE-1243
...
Release date:
| Status | ||
|---|---|---|
|
...
Issue
...
view tabs
Calculated and Comment fields (Hardcoded fields) won´t appear on screens where the Default or Field tabs are not selected.
...
Issue
...
Issue 9: The sum (Average) of numeric values in linked issues won't work with read-only fields.
...
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://trello.com/c/6HuVzQqj Issue 11: Forge custom fields are not supported by Jira automation of the box
...
Jira automation not fully supported
https://ecosystem.atlassian.net/browse/FRGE-1108Issue 12:
...
JWM list view
Forge custom fields do not work in JWM list view.
https://ecosystem.atlassian.net/browse/FRGE-1114 Issue 13:
...
Other third party apps (JXL, PowerBI)
Using Forge custom fields in other apps doesn’t always work as expected
| Status | ||
|---|---|---|
|
...
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.
...