...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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
...
Jira
...
Forge custom fields do not support inline editing on issue view.
https://ecosystem.atlassian.net/browse/FRGE-243
...
Jira cloud mobile app support
Forge custom fields do not work on Jira Cloud mobile app.
...
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.
...