Jira 10.3.5/Java 17 Plugin Compatibility Crisis with Atlassian SDK

Forge
,
1

Impact: Critical failure of the custom Workflow-Listener plugin following an upgrade of Jira Data Center from 9.12.7 to 10.3.5 and Java from 8 to 17. This is currently blocking PROD deployment work due to the loss of automated ticket-to-Bamboo linking and deployment triggering functionality.

Root Cause: The latest available development tool, Atlassian Plugin SDK (TGZ) 9.1.1 (compatible only up to Jira 10.0.1), is incompatible with the target Jira version and Java runtime.

Symptoms:

  1. Development Block: SDK 9.1.1 causes Maven build failures when targeting Jira 10.3.5.

  2. Runtime Failure: The custom plugin installs but is non-functional in Jira 10.3.5 (no logs/code execution), indicating a fundamental OSGi or Spring initialization failure due to breaking API changes in the Jira 10 platform (Platform 7).

Action Required:Urgent release date confirmation for an Atlassian Plugin SDK (or equivalent AMPS tooling) that officially supports Jira Data Center 10.3.5 (LTS) and Java 17, or immediate guidance on the required dependency updates to manually re-package the plugin.

Somebody please help me to get rid of this issue asap.

Thanks in advance,

Devendar G

2

Hi,

Please someone respond on this issue.

3

Hi @DevendarGangapuram ,

This may be better raised as an ECOHELP ticket directly with Atlassian.

For the most part this is a user forum for developers, and while Atlassian staff do visit from time to time (less so these days than in years gone by, it would seem), it is not an official support channel for getting help from Atlassian.

Additionally, it seems that your issue relates to JIRA Data Center, but you have posted in the category for Forge (which is the development platform for Cloud products), so any Atlassian staff that work on the DC side that read these forums may not have seen your issue.

Hope that helps.

2 Likes
4

Thank you @scottohara for letting me know this and for your inputs.

1 Like