Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Customized Plugin not working on 8.10.0 but working on 7.1.1

Sourav Bag September 25, 2020

Hi,

We are currently migrating JIRA Software from 7.1.1 to 8.10.0 . Now we have one customized plugin which is working perfectly on 7.1.1 but while deploying the same plugin on 8.10.0 , we are getting the below error in the log. Could you please help me figuring out the issue as i'm now to JIRA

com.atlassian.cache.CacheException: io.atlassian.util.concurrent.LazyReference$InitializationException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.xyz.jira.plugins.restrictedfields.adminonlyfields.RestrictedCheckboxFields': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.abs.jira.plugins.restrictedfields.adminonlyfields.RestrictedCheckboxFields]: Constructor threw exception; nested exception is java.lang.NoSuchMethodError: com.atlassian.jira.issue.customfields.impl.MultiSelectCFType.<init>(Lcom/atlassian/jira/issue/customfields/manager/OptionsManager;Lcom/atlassian/jira/issue/customfields/persistence/CustomFieldValuePersister;Lcom/atlassian/jira/issue/customfields/manager/GenericConfigManager;Lcom/atlassian/jira/issue/fields/rest/json/beans/JiraBaseUrls;Lcom/atlassian/jira/bc/issue/search/SearchService;Lcom/atlassian/jira/config/FeatureManager;)V
at com.atlassian.cache.memory.DelegatingCachedReference.get(DelegatingCachedReference.java:92)
at com.atlassian.jira.issue.search.managers.DefaultSearchHandlerManager.getHelper(DefaultSearchHandlerManager.java:240)

 

Thanks,

Sourav

3 answers

0 votes
Gianluca Tedeschi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 30, 2020

we have the same problems:

our custom plugin with our "custom field type"  work until 8.9.xxxxx but NOT in 8.10.x.

we are jira developers, we upgrade maven dependency to 8.10.1 and no compile errors are found... 

any suggestion??

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 25, 2020

The internal API in Jira changes in each version as functions in the software are added and updated.

In this case, your plugin is using a call that has been removed in version 8 (8 did a load of refactoring where deprecated stuff was removed completely).

You will need to rebuild the plugin from its source code, after updating it to match the version 8 API, or, if it's not your code, get a new version from the vendor, one that they've rebuilt for version 8.

0 votes
Pedro Felgueiras
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 25, 2020

Hi @Sourav Bag 

 

Do you have access to the source code of the plugin ? 

You now have two options:

  • Change the plugin to stop using deprecated functions
  • Live without the plugin 

 

If you don't have experience with developing plugins for Jira it could be a bit of a journey, but don't be to scary. 

Start reading some documentation here https://developer.atlassian.com/server/framework/atlassian-sdk/set-up-the-atlassian-plugin-sdk-and-build-a-project/

 

After being familiarized with how to build and modify your plugin your IDE will tell you what function you're using is deprecated. 

 

Good luck on your jurney !

Suggest an answer

Log in or Sign up to answer