The Adaptavist ScriptRunner for JIRA(v9.31.0) Upgrade Are there any expected issues?

[JungHyuk Kwon]

Hello.
I'm planning to upgrade to Adaptavist ScriptRunner for JIRA(v9.31.0)
Are there any expected issues?

[Plug-in]
Adaptavist ScriptRunner for JIRA / v8.36.0(AS-IS) to v9.31.0(TO-BE)

[License SEN]
Adaptavist ScriptRunner for JIRA: SEN-25032278

[Settings]
JIRA (D.C): v9.12.15 to v10.3.17
Java: JDK17 to JDK17
DB (MySQL): 8.0 to 8.0

Are there any other issues?
Please respond.
Thank you.

[Arkadiusz Wroblewski]

Hello @JungHyuk Kwon 

from a compatibility perspective your target stack looks fine (Jira DC 10.3.x + JDK 17 + ScriptRunner 9.31.x is a common combination). The risk is less “9.31.0 itself” and more the jump to Jira 10 plus any ScriptRunner breaking changes that hit your specific usage.

Things that typically cause trouble:

UI Fragments / web fragments (panels, links, buttons, web-resources): Jira 10 changed a few internals and older fragment setups can break.

Scripts depending on Jira internal APIs / removed libraries: Groovy code that imports classes that were available in older Jira versions may fail after the upgrade.

Behaviours / Listeners / Workflow functions: usually fine, but anything “custom” or using internal classes should be tested.

What I’d do:

Upgrade in staging first (copy of prod DB) and run a quick smoke test on:

Behaviours

listeners

workflow post-functions/conditions/validators

scheduled jobs

any Fragments you’ve configured

Check logs right after startup and after running the main scripts (you’ll spot missing class / dependency problems fast).

If you have any concerns (or you want a definitive “known issues for 8.36.0 → 9.31.0”), you should reach out directly to Adaptavist support with your exact Jira version, ScriptRunner version, and what ScriptRunner features you use (Fragments/Behaviours/etc.). They’re the only ones who can confirm product-specific edge cases for your environment.

Have a great Day 🤠 ☀️