Jira entity property limit in forge infrastructure

Forge Adopting Forge from Connect
, ,
1

We have a plugin that uses the Connect platform and works with Jira entity properties. This plugin has 43 different entity property values. We aim to migrate this plugin from Connect to the Forge platform, but the Forge platform limits the maximum number of Jira entity properties to 30. What solution would you suggest?

The application currently uses JQL functions that utilize Jira’s entity property feature. How can I migrate from Connect to Forge without requiring any additional action from users?

1 Like
2

Does putting multiple properties under one key work for you?

3

It is not possible due to our jql functions according to these entity property are used in customer systems. But I will try that added same allias(jql query such) from connect app to jql function module from forge. I think it will work beasue there is a sentece in jql function module about this.

"The name of the custom function.

Must be unique and different from the names of built-in JQL functions. In case of name collision, the built-in function will be called."

I know it refers to built-in JQL functions but maybe it works with old custom JQL functions from jira entity property.

4

Hi @KstebekTeknoloji Forge restricts the number of indexable entity property values to 30, this means they show up in search etc.

Could you elaborate on the app’s use case for having 43 entity properties? Is it critical that all are indexable as well?

5

Unfortunately all of 43 entity property is used for JQL custom function. Here is our app JQL reference page.

Link : JQL Reference Page

We don’t know how many user used for those jql functions on their filters etc.

So we have to migrate all of functions with same syntax. If not, all users must change their filters.

@reddy1 any suggestions?