Breaking Changes
Version 9.0.0+
Bitbucket was updated to version 9
See the Atlassian Bitbucket 9 release notes for details. See the Upgrade page for more information on compatibility and how to upgrade.
Gray API removal
Previously, apps could access code from third-party libraries. If you are using any third-party APIs (or Gray APIs), your scripts could break. Please review Atlassian documentation for the full list of removed APIs.
Other API changes
Atlassian has made other API changes you should be aware of, see the API changelog for further details.
Fragments updates
Please check out these pages to see what's changed with our UI Fragments:
- Raw XML Module Breaking Change for Bitbucket 9
- The formats for
condition class
andprovider class
have changed.
- The formats for
- Web Resource Breaking Change for Bitbucket 9
- If you have files in
plugin.resource.directories
you will have to move them toweb-resources/com.onresolve.stash.groovy.groovyrunner
.
- If you have files in
- Web Panel Breaking Change/Deprecation for Bitbucket 9
- The
writeHtml
method will now be ignored. - Atlassian's
WebPanel
interface has moved to a new location.
- The
Version 8.0.0+
Groovy was updated to 4.0.7
See Groovy 4 Update section for details.
Deprecated SrSpecification class removed
Authors of Script Plugins may be used to writing tests which extend the deprecated com.onresolve.scriptrunner.canned.common.admin.SrSpecification
class. This class has been removed. Authors of tests for their scripts should extend the spock.lang.Specification
class directly. The Test Runner Built-in Script should still pick up tests as normal.
Version 7.0.0+
Groovy Updated to 3.0.12
See Groovy 3 Update section for details.
Spock Updated to 2.0
As part of upgrading to Groovy 3 we had to update Spock, because there is no Groovy 3 compatible version of Spock 1.3, which was used in ScriptRunner 6.
Spock can be used to write and run unit tests within ScriptRunner. It is unlikely that tests written by ScriptRunner users would use parts of Spock 2.0 that contain breaking changes. However, if you maintain tests for your scripts you should explore the breaking changes listed in the release notes for Spock 2.0.
JUnit 4 Removed
Although it wasn't advertised in the documentation, it was possible to write and run unit tests using JUnit 4 in ScriptRunner 6. Spock 2.0 is based on JUnit Platform, not JUnit 4, so JUnit 4 tests will no longer work inside ScriptRunner.
If you wrote any tests using JUnit 4, then you will need to rewrite them using Spock.
Version 6.17.0+
IE11
The last ScriptRunner for Jira version compatible with IE11 is 6.17.0. Do not update ScriptRunner past this version if using IE11.