Limitations

This section summarizes key limitations when using External Data for Jira Fields.

Field Configurations

The number of field configurations you can create is limited by your subscription plan. Refer to the feature plan matrix for more details.

Field Options Sync

• The List Type has a limitation of 7.000 values – but keep in mind, the dropdown performance in the issue view starts to decrease drastically at around 2.000 entries. The performance also depends on the machine you are testing it on, so make sure your userbase can use it properly.

• The Dictionary Type has limitation of 6.000 key value pairs

• The Cascading List Type has a limitation of 1.000 parent options

• The Cascading Dictionary Type has a limitation of 1.000 parents and 1.000 child elements, but not more than 10.000 elements in total.

• The maximum number of fields for Dictionary Type and Cascading List Type combined is 100.

The type Field Options Sync can only sync to global custom fields.

Search Field

Due to cloud limitations for connect Apps a Search Field cannot be placed on the Jira Create Issue Screen or Transition Screens.

Update: Please consider using the Extension Search Fields feature, which can be added to the Jira Create Issue Screen.

Dependant Field

To prevent looping, our system ignores issue events if an update occurs within 5 seconds of a previous update.

Data Sources

Due to memory and parsing load on our infrastructure, a data source cannot load more than 15MB of data per request. Once the limit is reached, a request will fail to load properly. If you have a use case in which more data needs to be processed, please get in touch with us.

The number of data sources you can create is limited by your subscription plan. Refer to the feature plan matrix for more details. You can work around this limitation by using variables which makes a data source more versatile.

Pagination Data Source

The maximum amount of pages that can be loaded is defined by either the amount of items or value of maximum page size. Below 10.000 items the max page size is 20 and above 10.000 items the max page size is 6.

The total bytes of all cumulated pages cannot surpass the response limit of 15 MB

Salesforce

Salesforce limits each user to 5 active refresh tokens. Creating more than 5 data sources with the same account will revoke earlier ones.

The maximum number of rows returned by SOQL over the REST API is 2.000 per request. You can workaround this limitation by using Salesforce Pagination

XML Support

Not all features are fully supported or function optimally with XML. To access the full range of features, consider using a JSON data source instead.

General

Email User Context

Accessing the email address of a user can work in some cases depending on their privacy settings, but will be empty in most cases. Due to the GDPR compliance you should use the accountId of a user instead, which is a reliable identifier of a user. In case you want to map an email address from your data source to an accountId we offer this workaround – but mapping an accountId to an email address is not possible. There is a workaround by using automation to expose email addresses if really needed (You should be aware of implications).

JSM Request Screen

Only user values can be accessed and used for dependancies in the create request screen. Other issue values can solely be used after the ticket is created.

Positioning of a Search Field or Info Panel is always at the bottom of the form due to cloud limitations.

Unauthenticated customers are currently not supported and are unable to view the fields.