Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Forge Custom Fields on new issue navigator view and boards

Description

We plan to render Forge custom fields on

  • Issue Search / Filters (NIN new issues navigator view)

  • Boards (Card Layout)

Probably we will use Formater, and the ability to popup a dialogue.
We plan to start the exploration in March we will keep you posted.
Don’t hesitate to share your use case with us.

 

Orgnial request description

The current Forge CustomField is not beeing rendered in a lot of Jira Views:

  • Issue Search / Filters

  • Boards (Card Layout)

  • Dashboard Gadgets like Filter Result

  • Next-Gen Issues

As a result it's difficult for the users to view the status for lot of issues at first glance
Currently it would look like this


While in a server environment something like this is possible

Attachments

5

Confluence content

mentioned on

Marcel HerrmannJuly 23, 2024 at 9:41 AM

Just wanted to Atlassian know that this is still an active issue for us. By now the technical blockers seems to be resolved for us to implement forge with our plugin. While this feature is not a technical blocker, it’s a huge visual gap to be only able to render some text.

As a deverloper myself I can see some of the technical challenges a feature like this needs to address, but without this the feature there will always be a huge usability / visual gap between Cloud / DC Apps. Currently the CustomField renderer is used at the only view, where there are already a huge amount of extenstion points

Krzysztof KerczJune 18, 2024 at 12:08 PM

Hey, , for access to user’s locale, follow

Floating ElectronJune 18, 2024 at 10:00 AM

I would like to add that if in those places formatter is used, we require additional context in the Jira expression, specifically the user's locale in our case. It would allow us render correct translations for fields

Niklas SchlögelJune 3, 2024 at 9:03 AM

We actually did receive at least 2 or 3 customer requests, because they expect to see Custom Field values (that we implemented with the Forge Custom Fields module) in their Backlog view. Just to add a factor on that topic.

Jakub MierzewskiMay 30, 2024 at 11:52 AM

there are always more factors that are taken into consideration

  • effort

  • impact to customers

  • is it needed for Apps migrating from the Server or Connet

  • dependencies to other teams

  • needed skillset

and more