Power Database Fields is compatible with:

• Jira Data Center: 8.20.0 - 10.x

Current app versions available:

• v7.1.1000.2 (latest) compatible with Jira Data Center 10.0.0 - 10.x

• v6.3.820.2 compatible with Jira Data Center 8.20.0 - 9.x

If you have installed an incompatible version of Power Database Fields on your Jira instance, perform the following steps:

1. Uninstall the SIL Engine and Power License Manager apps.

2. Uninstall the Power Database Fields app.

3. Install the version of Power Database Fields that is compatible with your Jira version.
   SIL Engine should get updated automatically and should now have the correct version as well.

One common performance issue occurs with Autocomplete fields when dealing with large result sets. If you're experiencing slow loading times when the number of search results is very large, adjusting the Minimum Characters setting can significantly improve performance.

To adjust the setting, go to your field configuration and increase the Minimum Characters value to reduce the frequency of database queries.

• Default setting: 2 characters. This means a new database request is triggered for every keystroke after the 2nd character (including subsequent characters). With longer search terms, this can result in multiple rapid server requests in a short time period.

• Recommended for large datasets: Increase to 5 or more characters. By increasing this value to 5, the search will only begin after users type at least 5 characters. This significantly reduces server load and speeds up response times, especially when there are many possible matches in your dataset.

Power Database Field executes an SQL query each time a user accesses a screen containing one of the custom fields. The custom field's performance is directly tied to the underlying database query performance.

• If your query takes 10 seconds when executed directly in the database console, the custom field will also take 10 seconds to load.

• Multiple concurrent users amplify this effect—for example, 5,000 users each triggering a 10-second query when creating or editing issues can significantly impact your database performance.

• This performance behavior applies to any database plugin custom field, not just Power Database Fields.

Suggested optimization strategies to improve performance include:

If your database custom fields are missing or appear to have lost data after updating Power Database Fields, this is likely due to upgrading from version 5.8 or earlier to version 6.0+ without performing the required migration.

What happened: Power Database Fields version 6.0+ only supports next-generation fields (Advanced Database Row Field and Advanced Database Table Field). Legacy fields were completely removed in version 6.0 as part of a major architectural change.

The solution: You must migrate your legacy fields before upgrading to version 6.0+. If you've already upgraded without migrating:

1. Downgrade to your previous version (5.8 or earlier) if possible.

2. Migrate your legacy fields to the new Advanced Database Fields.

3. Upgrade to version 6.0+ after migration is complete.

Power Database Fields enables you to import data from an external database into database custom fields in your Jira. You can execute various types of queries and when data is retrieved, users can select from the results using select lists or autocomplete boxes.

The method for using custom field values in SQL queries depends on which version of Power Database Fields you're using.

For Advanced Database Fields (version 6.0+)

If you're running Power Database Fields version 6.0 or later, you're using next-generation Advanced Database Fields:

• Advanced Database Row Field

• Advanced Database Table Field

When working with advanced database fields, you can reference custom field values in your SQL queries using script parameters. Configure these queries through your Advanced Database Field configuration page. 

For Legacy Database Fields (version 5.8 and earlier)

If you're running Power Database Fields version 5.8 or earlier, you're using legacy database fields that include:

• Database Information custom field

• Database Child Information custom field

• Database Row custom field

• Data Table custom field

When working with legacy database fields, you can reference custom field values in your SQL queries (typically in the WHERE clause) by using the custom field ID (e.g., customfield_12345) or standard fields between braces. Configure these queries through the Database Custom Field page.