Migrating from PCF® PRO to Power Custom Fields®

Owned by Radu Dumitriu (Deactivated)
Last updated: May 06, 2020 by Chelsea Bauer (Deactivated)

This page is intended for users that already use Power Custom Fields® PRO and Power Custom Fields® in the same time.

If you are a first time user of Power Custom Fields®, feel free to skip this page.

Meet Power Custom Fields®

As part of our revised strategy, we have decided to move all custom fields® functionality into a one Power Custom Fields® app that would be your ultimate go to plugin for the custom fields. Having several custom field apps has spread our efforts on multiple fronts. With this move, we aim to consolidate our offering and lay out the foundation for the next great things to come.

Notes for the Power Custom Fields® PRO users

Fields defined by Power Custom Fields® PRO will continue to work in the same way as in the Power Custom Fields®. No changes are expected or intended.

If you have Power Custom Fields® PRO already and installed Power Custom Fields®, consider the following precautionary measures:

  1. If you have a valid license of PCF PRO™, you are entitled to a PCF™ license. Contact us, and we'll help migrate your license from PRO to PCF™ edition.
  2. All custom fields defined by PCF PRO™ will be migrated automatically  along with their configuration. This step cannot be reversed easily, however you can contact support if you want to reverse it manually (you will need to run certain SQLs on your database). We must insist here, this is a step we highly do not recommend.
    Migrating your PRO license is the only correct thing to do, as new improvements and maintenance will only happen in PCF™ from now on.
  3. Both PCF PRO™ and PCF™ will continue to function in parallel, however we strongly recommend that you uninstall the PCF PRO™ at your earliest convenience because the migration task happens only once. 
  4. Do NOT create more custom fields via PCF PRO®. You have all functionality in the PCF® edition.
  5. After installing PCF® and uninstalling PCF PRO® we strongly recommend you to restart Jira and perform Jira re-index.

Troubleshooting

We have worked hard so that PCF™ and PCF PRO™ work in parallel so it will allow you to switch the editions easily. However, if you encounter problems during your migration, here's a list of known issues.

SymptomHow to solveExplanation

You have have both Power Custom Fields® and Power Custom Fields® PRO and cannot update the configuration of the existing fields. 

When you click the referring link, a 404 error appears.

  1. Uninstall the old PCF PRO™ plugin
  2. Perform a disable/enable cycle the PCF™.


We recommend the disable-enable cycle on the PCF™ in order to be sure that the new add-on is in effect. Another option for you is to restart Jira after you uninstall PCF PRO™.

all fields from PCF® PRO get migrated and this might cause certain conflicts between the two versions
LOG custom field is missing / not renderedRemove that custom field, it is not provided by Power Custom Fields® anymore.There are better options to deal with the log at this moment. Specifically, SIL™ Manager got itself a new runner and a log viewer. Stay tuned!

After un-installing Power Custom Fields® PRO, the migrated fields work perfectly but the administration pages return the 404 error (not found). The following or similar exception text appears in the logs:

org.picocontainer.injectors.AbstractInjector$UnsatisfiableDependenciesException:

com.keplerrominfo.jira.plugins.keplercf.smartselect.optionscf.config.view.EditSilOptionsCFConfig has unsatisfied dependency

'interface com.keplerrominfo.jira.commons.hostapp.JMUserServices' for constructor 'public com.keplerrominfo.jira.plugins.keplercf.smartselect.optionscf.config.view.EditSilOptionsCFConfig(

com.keplerrominfo.jira.plugins.keplercf.smartselect.optionscf.config.ConfigurationParametersService,

com.keplerrominfo.jira.plugins.keplercf.smartselect.optionscf.config.ds.DataSourceFactoryRegistry,

com.keplerrominfo.warden.addon.LicenseStatusService,

com.keplerrominfo.jira.commons.user.CurrentUserHelper,

com.keplerrominfo.jira.commons.hostapp.JMIssueServices,com.keplerrominfo.jira.commons.hostapp.JMUserServices)'

from org.picocontainer.DefaultPicoContainer@15e86fad:

1<[Immutable]:com.atlassian.jira.component.pico.CachingMutablePicoContainer@737befef

        at org.picocontainer.injectors.ConstructorInjector.getGreediestSatisfiableConstructor(ConstructorInjector.java:191)

        at org.picocontainer.injectors.ConstructorInjector.getGreediestSatisfiableConstructor(ConstructorInjector.java:110)

[ ...... rest of the stack trace removed for brevity .... ]

Restart Jira

 - or -

Restart Power Custom Fields® (execute a Disable - Enable in the 'Manage Add-ons' Jira administration page)

We do not have an explanation yet on why this is happening. It affects Jira servers randomly, and so far we were not able to solve this completely.

Some Spring beans references exposed by the Warden and SIL™ Engine companion add-ons are lost. Normally un-installing the PCF PRO™ shouldn't touch the existing SIL™ Engine and Warden add-ons, but for whatever reason it happens.

We are working on a solution, and will update this page when we have an update.

Additional Assistance

For additional assistance open a support request here.