Missing Forge features

As you're aware, we've adopted Atlassian's Forge platform for developing our app, leveraging its numerous benefits, particularly in terms of security, privacy, and expedited feature development and deployment.

However, it's worth noting that while Forge offers significant advantages, there are still certain entry points and functionalities that are not yet supported. Enclosed in this compilation are items that currently fall outside the platform's capabilities. For your reference, we've included the corresponding tickets within the Atlassian Forge project.

Can Awesome Custom Fields be used in all Jira views?

Awesome Custom Fields are optimized for the issue view, which aligns with our intended usage for these fields.

While we acknowledge that Jira offers various views, it's important to note that not all of them are currently supported by Forge.

Our fields cannot be displayed as images in the issue navigator, lists, boards, or cards. Instead, a text representation will be shown.

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

Can Awesome Custom Fields be used in all Jira screens?

Awesome Custom Fields function smoothly within the create and edit issue screens. However, there are limitations when it comes to transition, workflow and create subtasks screens, as well as in bulk edit.

Regrettably, we're unable to offer graphical inputs for setting values for our fields in these contexts.

Instead, users are required to utilize object notation (JSON), which can be found for each field in the respective field documentation.

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

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

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

Can Awesome Custom Fields be used in team-managed projects?

Awesome Custom Fields are optimized for company-managed projects. While you may use our fields in team-managed projects, there are some drawbacks to consider.

One significant limitation is that our custom fields, as well as those from other third-party apps, cannot be created within the specific project scope. Consequently, these custom fields must be created globally by an administrator before they can be utilized by the project lead.

Support for creating App project-scoped custom field types in team-managed projects

Can Awesome Custom Fields be used in Jira automation?

Third-party fields cannot be used in the basic mode for fields in automation. Find out more Use custom fields with automation

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

Can Awesome Custom Fields be used in Jira Service Management?

Yes! You simply install our JSM extension

So we provide a workaround for this: https://ecosystem.atlassian.net/browse/FRGE-778

Please also note that Forge custom fields are not rendered in the queue. Instead, a text representation will be shown.

Can Awesome Custom Fields be used in Jira Work Management projects?

You may use our fields like in every other Jira project. Some features, including the advanced issue table with inline edit, may not be available for third-party fields.

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

Can I use user impersonate with Forge?

Unfortunately you can’t use ACF fields with the user impersonate function. You’ll get something like this

Open

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

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