Open

Release date: Aug 12, 2022

This page includes the breaking changes introduced to Power Database Fields that can affect your existing system. Review the changes carefully and perform any necessary actions to maintain the app’s functionality.

Jira compatibility: Jira 8.20.x and Jira 9.0.

Overview

This release removed all legacy database custom field types that were deprecated in version 5.8. This change breaks backward compatibility and requires mandatory migration before upgrading. Legacy field configurations will become inaccessible in the Jira UI after upgrading to version 6.0+, though data remains in the database and can be restored by downgrading to version 5.8+.

Removal of legacy Database Power Field types

Power Database Fields version 6.0.820.0 completely removed all legacy database custom field types that were previously available in versions 5.8 and earlier. This change affects customers who have existing implementations using any of the deprecated field types.

• Last version with legacy support: Version 5.8.0.14 was the last version to support legacy fields, which were deprecated in version 5.8 (June 2021) and completely removed in version 6.0+.

• Migration path required: Customers must:

  • Upgrade to version 5.8+ first.

  • Migrate legacy fields using the Migration Wizard or manually reconfigure fields using a new field type.

  • Then upgrade to version 6.0+.

Affected fields

Impact

• Legacy field configurations become inaccessible in the Jira UI after upgrading to version 6.0+.

• Existing field data remains in the database but cannot be displayed or modified through the interface.

• Custom field IDs change during migration (new fields receive new custom field IDs).

• JQL queries using legacy field references require updates to new field IDs.

• SIL scripts (or any other automation) referencing legacy fields must be updated for the new field structure.

• Database storage format changes from plain text values to JSON format, potentially breaking external automations or integrations that directly access Jira's internal database.

Benefits

Next-generation fields provide:

• Enhanced performance and UI improvements: Improved query execution, field responsiveness, and updated user interface components.

• Simplified architecture: Consolidates four legacy field types into two comprehensive solutions, reducing configuration and maintenance complexity.

• Extended functionality: New capabilities including direct database insert/update operations on external data sources.

Migration requirements

Customers upgrading from version 5.8 or earlier to version 6.0+ must complete a mandatory migration process:

1. Pre-migration: Upgrade to the latest version 5.8+ (recommended: 5.8.0.14).

2. Migration execution: Use the Migration Wizard or manual migration process to convert legacy fields.

3. Validation: Test migrated fields in a development environment to ensure proper functionality.

4. Value transfer: Run SIL scripts if field values require manual transfer (complex configurations).

5. Post-migration: Update any JQL queries, SIL scripts, or integrations referencing old field IDs.

6. Version upgrade: Upgrade to version 6.0+ only after successful migration completion.

Mitigation:

• Data preservation: Legacy field data remains in the database and can be restored by downgrading to version 5.8+.

• Recovery path: If migration issues occur, customers can downgrade to resolve problems before re-attempting migration.

• Testing environment: The Migration process should always be performed in a test environment before production implementation.

• Backup requirement: Database backup is mandatory before beginning the migration process

Configuration complexity considerations:

• Simple configurations: Fields with basic queries typically migrate successfully using the Migration Wizard

• Complex configurations: Fields with advanced SQL queries, complex relationships, or custom scripts might require manual reconfiguration

• Child field relationships: Legacy child field concepts must be redesigned using multi-column Advanced Row Fields or dynamic parameter relationships