Release 9.x

9.1.1

Compatibility with Jira 10

ScriptRunner for Jira is now compatible with Jira 10. See the Compatibility with Jira page for more information on Jira 10 best practices on upgrading your instance.

Breaking changes

There are some key breaking changes you should be aware of when upgrading to Jira 10:

• Third-party library/API removal
• JDK has been updated. The minimum supported version of the JDK is now JDK 17. 
• Fragments updates (see more below)

See the breaking changes page for the full details of all breaking changes related to this upgrade. 

Fragments updates

To adhere to Jira 10, UI Fragments had the following changes: 

• Raw XML Module Breaking Change: Fragment XML conditions scripts and web panel class scripts are now provided via XML parameters and are no longer directly set as the condition class element attribute or the web panel class element attribute value. The previous formats no longer work in Jira 10 versions of ScriptRunner. You can use the Raw XML Module Breaking Change guide to help you convert your scripts to the new fragment XML parameters format. Major changes include: 
  • Format of the XML condition class attribute and user scripts now added as parameters
  • Format of the XML Web Panel class attribute and user scripts now added as parameters

• Web Panel Breaking Change/Deprecation for Jira 10: If you used a com.atlassian.plugin.web.model.WebPanel class implementation for the provider class/script of your web panels, the way this is processed will be different after upgrading to Jira 10. Check out the Web Panel Breaking Change/Deprecation for Jira 10 guide to learn how to update scripts. Major changes include: 
  • The writeHtml method is now ignored
  • The Atlassian com.atlassian.plugin.web.model.WebPanel interface is deprecated and has moved to a new location
• Web Resource Breaking Change: If you have files in plugin.resource.directories you will have to move them to web-resources/com.onresolve.jira.groovy.groovyrunner. Check out the Web Resource Breaking Change page to learn more.

• Web Item Provider Built-In Script: Major changes include:

  • The feature will only function once Jira releases the new fragment API updates (Estimated to be available from Jira 10.1.0/10.0.2). See the ticket for updates.
  • The com.atlassian.plugin.web.api.model.WebFragmentBuilder API has moved to com.atlassian.plugin.web.model.WebFragmentBuilder. Any scripts using the old API import will need to be updated to the new location. (Once updated, your scripts will no longer show a red line under the old import; however, you cannot verify the fix fully until Atlassian releases the API mentioned in the ticket.)

Backward compatibility

ScriptRunner 9.1.1 will only support Jira 10.0 and above and will not be backwards compatible with earlier Jira versions. Critical bugs and security fixes will continue to be released for ScriptRunner 8.x.x. We recommend users on older versions of Jira or ScriptRunner plan their upgrade to ensure access to the to ensure access to the latest features, performance improvements, and security enhancements. We recommend following our Compatibility with Jira page for information and recommendations on how to upgrade.

Tempo compatibility

ScriptRunner for Jira Data Center is currently not compatible with Tempo after the Jira 10.0 upgrade. We aim to be compatible with Tempo soon.

Bugs fixed