Issues with upgrading Power Custom Fields
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
ℹ️ Always contact the Power Custom Fields Support Team before testing your environment.
Power Custom Fields Custom fields are not showing up on an upgraded Jira version.
Diagnosis
Run the following query to check if the app key is correct:
1
select * from customfield where cfname = "Power Custom Field cfname";Note that cfname, in this case, is an example. Please check the proper name on your environment.
Problematic result:
1
2
CUSTOMFIELDSEARCHERKEY:
com.keplerrominfo.jira.plugins.keplercf-pro:socfExactSearcherNote the keplercf-pro on the string.
Expected result
1
2
CUSTOMFIELDSEARCHERKEY:
com.keplerrominfo.jira.plugins.keplercf-pro:socfExactSearcherCause
For some unknown reason, when Power Custom Fields was updated over the years on the customer environment, the plugin key should update when the addon is updated, but in this case, something did not go as expected.
Solution
Contact Power Custom FieldsSupport to analyze this issue and help with the solution.
Was this helpful?