Hello,
We are experiencing a JIRA custom plugin issue due to latest unavailable of compatible Atlassian SDK for the JIRA 10.3.x on the marketplace.
**Issue Summary:**Our Jira Data Center instance has been upgraded from 9.12.7 to 10.3.5 and the underlying Java runtime has been upgraded from Java 8 to Java 17 to address security vulnerabilities.
The custom Workflow-Listener plugin—essential for automatic JIRA ticket linking in Bamboo comments and triggering UAT/PROD deployments via workflow transitions—is now non-functional in the new environment. The plugin installs in Jira’s ‘Manage Apps’ but exhibits no expected behavior (no logs, no code loading).
The existing development environment, using Atlassian Plugin SDK (TGZ) version 9.1.1, is incompatible with the new Jira/Java stack, leading to Maven build failures when attempting to re-package the plugin.
Environment
PROD work blocker
Hello @DevendarGangapuram
This forum is not an official support channel for getting help from Atlassian. Copying and pasting essentially the same question that you’ve already asked into a new forum thread won’t achieve much.
Your question may be better raised as an ECOHELP ticket directly with Atlassian. Since you have Jira Data Center, your license entitles your organization to get support on such matters.
I hope that helps.
As a side topic, when your organization did a test of upgrading their Jira DC instance from 9.12 to 10.3 in a sandbox environment, and discovered the effect the upgrade would have on that apparently ‘critical’ legacy plugin, why did they proceed to perform the upgrade on their production instance without first determining if the problem with that plugin could actually be solved? Asking for for a solution to a problem that you knew would happen as a result of doing the upgrade seems bizarre!