Jira Unknown Add-ons

[Hadi A]

Hi,

I recently installed an add-on, found out it was the wrong version, uninstalled it, then tried to install the correct version (which failed).

This resulted in a couple of unknown add-ons to show up in the UPM which I cannot get rid of (screenshot below). Any idea on how I can remove them? They are blocking the installation of any other add-ons?

[Andy Heinzer]

Try to restart Jira.  The screenshot you posted shows that those plugins are not loaded into Jira.  If you already removed the other plugin then restarting Jira could clear out some other caches that might not have yet cleared.

If you find you still cannot install this other plugin please check these things in this order:

1. Do you still see the same plugins in the UPM after a restart of Jira?
2. Check the Jira log $JIRAHOME/log/atlassian-jira.log during startup.  If Jira is still trying to load some additional plugin here, then perhaps there is another .jar or .obr file in the $JIRAHOME/plugins/installed-plugins/ folder that Jira is trying to load.
3. Try running the following SQL command against your Jira database and let me know the results:

   select * from pluginstate;

The last query will tell us what plugins are disabled in the database of Jira from starting.

If you are still stuck after doing all of these, please also let me know

1. What version of Jira is this?
2. what plugin you installed initially and it's version,
3. and then what version you are trying to install after the fact.

Thanks

Andy

[Hadi A]

Hi,

Thanks for your response. As it is a production environment, I will be able to validate this over the weekend and get back to you.

Thanks!

[Hadi A]

Hi, 

Sorry for the late reply.

Jira Version: DC 7.8 

The plugin initially installed was: https://marketplace.atlassian.com/apps/1214668/insight-discovery?hosting=server&tab=versions

I am trying to install it again :) 

Below is the result of 

select * from pluginstate;

com.atlassian.jira.plugins.workinghours false
com.atlassian.plugin.automation.jira-automation-plugin true
com.atlassian.psmq true
com.atlassian.servicedesk false
com.atlassian.servicedesk.application false
com.atlassian.servicedesk.approvals-plugin false
com.atlassian.servicedesk.frontend-webpack-plugin false
com.atlassian.servicedesk.internal-base-plugin true
com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin false
com.atlassian.servicedesk.plugins.automation.servicedesk-automation-plugin true
com.atlassian.servicedesk.plugins.automation.servicedesk-automation-then-webhook-plugin false
com.atlassian.servicedesk.plugins.servicedesk-search-plugin false
com.atlassian.servicedesk.project-ui false
com.atlassian.servicedesk.public-rest-api false
com.atlassian.servicedesk.servicedesk-canned-responses-plugin false
com.atlassian.servicedesk.servicedesk-knowledge-base-plugin false
com.atlassian.servicedesk.servicedesk-lingo-plugin false
com.atlassian.servicedesk.servicedesk-notifications-plugin false
com.atlassian.servicedesk.servicedesk-reports-plugin false
com.atlassian.servicedesk.servicedesk-variable-substitution-plugin false
com.awnaba.projectconfigurator.projectconfigurator false
com.botronsoft.jira.configurationmanager true
com.botronsoft.jira.rollout.configuration-manager-core true
com.botronsoft.jira.rollout.integrity-check true
com.burningcode.jira.plugin.jiracomponentwatcher true
com.caritteprod.group-ambassadors false
com.coresoftlabs.pulse_monitor.pulse_monitor false
com.eazybi.jira.plugins.eazybi-jira true
com.googlecode.jira-suite-utilities false
com.infosysta.jira.mobile false
com.innovalog.jmwe.jira-misc-workflow-extensions false
com.kostebekteknoloji.plugins.jira.zephyr-report false
com.kostebekteknoloji.plugins.jira.zephyr-report:applicationProperties true
com.midori.jira.plugin.pdfview false
com.onresolve.jira.groovy.groovyrunner true
com.riadalabs.jira.plugins.insight true
com.tempoplugin.tempo-accounts false
com.tempoplugin.tempo-core false
com.tempoplugin.tempo-plan-core false
com.tempoplugin.tempo-planner false
com.tempoplugin.tempo-platform-api false
com.tempoplugin.tempo-platform-jira false
com.tempoplugin.tempo-teams false
com.thed.zephyr.je false
com.thed.zephyr.je:zephyr-rest-filter true
com.thed.zephyr.zapi false
com.wittified.delegated-group-management-in-jira true
de.polscheit.jira.plugins.gantt false
es.excentia.jira.plugins.jira-traceabilityx-plugin false
eu.softwareplant.bigpicture true
info.renjithv.jira.plugins.sysadmin.homedirectorybrowser false
pl.com.tt.apdc.vacation-manager false
plugin.jip true
plugin.jip:ao true
ru.andreymarkelov.atlas.plugins.signaturefields true
tac.jira software.languages.cs_CZ false
tac.jira software.languages.da_DK false
tac.jira software.languages.et_EE false
tac.jira software.languages.fi_FI false
tac.jira software.languages.hu_HU false
tac.jira software.languages.is_IS false
tac.jira software.languages.it_IT false
tac.jira software.languages.nl_NL false
tac.jira software.languages.no_NO false
tac.jira software.languages.pl_PL false
tac.jira software.languages.ro_RO false
tac.jira software.languages.sk_SK false
tac.jira software.languages.sv_SE false
tac.jira software.languages.zh_CN false

[Andy Heinzer]

Thanks for that info.  I can see that the insight plugin looks to be set to be enabled.  I am starting to wonder if this is a case where the plugin code could be different for a Data Center deployment versus a Server deployment.  There are significant differences between these deployment types such that if you're trying to install a Server plugin to a data center install, it might not behave the way the vendor expected.  I can see from the marketplace page of https://marketplace.atlassian.com/apps/1214668/insight-discovery?hosting=datacenter&tab=overview

There is a data center option that should be selected here. It looks like this plugin vendor has a different .jar file for data center vs server.   In your case, I would recommend downloading that latest Data center release, from https://marketplace.atlassian.com/download/apps/1214668/version/202000050

If you download the Server version, it appears to have the same versioning numbers, but I expect this code to be slightly different.