We want to disable Issue Alternate Assignee plugin through Oracle Database

[vasantha kumar K R]

Hi,

We upgraded JIRA from 6.0.3 to Jira 6.4. After upgrade when we launch JIRA through browser, a fatal error is thrown org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.iamhuy.jira.plugin.customfields.UserPickerProjectRole'

We understood that Issue Alternate assignee plugin is causing this problem so we want to disable this plugin through database. We are using Oracle 11g database. Can you help us with the query as to how to disable this plugin through database. We request your kind attention as we this is critical and we need to fix this quickly.

Regards,

Prashant

[Vasiliy Zverev · Accepted solution]

It seems that you have uncompatible version of plugin. 

According to documentation it does not have version compatible both with 6.3 and 6.4. 

It will be better to try upgrade plugin first.

[vasantha kumar K R]

Hi Vasiliy,

Thanks for quick response. We have already upgraded and Jira is not starting because of this error. We have only two options here:

1. Roll back to 6.0.3, disable Issue Alternate assignee plugin and then upgrade to 6.4
2. Disable this plugin from database.

Rollback is quick option, but we want to try disabling this addon through database and see whether it works.

Its highly appreciated if you help us with database part.

[Vasiliy Zverev]

You could lost date stored into custom filed provided by this plugin.

Since it is more reliable to downgrade to 6.3, install compatible version of plugin and restore data from xml backup

[Nic Brough -Adaptavist-]

Please don't try to do this in the database, it's not safe or even easy.

If you stop JIRA and remove the physical add-on, JIRA should recognise that and disable it cleanly itself on restart.  Have a look in <jira-home>/plugins/installed-plugins - most have a recognisable name, and you can move it (don't delete, you might want to put it back) to a safe place in your home directory.

[Prashant Hiremath]

Thank you @Nic Brough [Adaptavist] and @Vasiliy Zverev for not suggesting to manipulate database directly.

I replaced the jar file of Issue Alternate Assignee plugin(v.1.7.8) with the one compatible for JIRA 6.4. It worked for me and the this time the JIRA  instance did start properly.

Thank you all once again !!!