...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Info |
---|
This page is intended for users who already use Power Custom Fields PRO and Power Custom Fields simultaneously. If you are a first-time user of Power Custom Fields, feel free to skip this page. |
...
You are entitled to a PCF license with a valid PCF PRO license.
Contact us, and we'll help migrate your license from PRO to PCF.
All custom fields defined by PCF PRO will be migrated automatically along with their configuration.
Note that this step cannot be reversed easily.
You must contact support and reverse it by running specific SQL scripts on your database.
This process is not recommended.
Migrating your PRO license is recommended, as new improvements and maintenance will only be implemented into PCF.
Both PCF PRO and PCF will continue to function in parallel. However, we strongly recommend uninstalling PCF PRO at your earliest convenience because the migration task happens only once.
Do NOT create more custom fields via PCF PRO. All PCF Pro functionality exists in PCF.
After installing PCF and uninstalling PCF PRO, we strongly recommend restarting Jira and performing a Jira re-index.
...
Symptom | How to solve | Explanation |
---|---|---|
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. |
| All fields from PCF PRO are migrated and this might cause certain conflicts between the two versions. |
LOG custom field is missing / not rendered | Remove the custom field. It is no longer provided by Power Custom Fields. | There are better options to deal with the log at this moment. Specifically, SIL Manager’s new runner and 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). | This error affects Jira servers randomly, and currently, there isn’t a fix. Some Spring beans references exposed by the Warden and SIL Engine companion add-ons are lost. Normally un-installing PCF PRO shouldn't touch the existing SIL Engine and Warden add-ons, but it does occasionally happen. We are working on a solution. |
...