Is it possible to increase the 30-field limit for jira:entityProperty indexing in Forge?

Forge Adopting Forge from Connect
,
1

Hi team,

I’m currently migrating a Jira Connect app to Forge and have run into a limitation with jira:entityProperty indexing.

In Forge, the documentation states:

“The list of fields in the JSON object to index with the type of each field.
The maximum number of elements to index is 30. This means that all your jira:entityProperty modules combined can’t declare more than 30 values.”

In my existing Connect app, we are indexing around 90 entity properties (used across multiple features, JQL queries, and dashboards). This design has been stable and widely used by customers for years.

My questions are:

  1. Is there any way to increase or bypass this 30-field indexing limit in Forge?

  2. Are there any recommended architectural patterns for apps that need to query a large number of properties (e.g. grouping, denormalization, multiple entities, or alternative storage like Forge SQL)?

  3. Is this limit hard and permanent, or are there plans to raise it in the future for more complex apps migrating from Connect?

This limitation is currently a major blocker for our migration, so any guidance or official recommendation would be greatly appreciated.

Thanks in advance!

3 Likes