Jira Service Management 5.17.x upgrade notes
Below are some important notes on upgrading to Jira Service Management 5.17.x. For details on the new features and improvements in this release, see:
Upgrade notes
Assets automation causes a silent failure
We’ve identified an issue where Assets automation rules might not trigger after upgrading to Jira Service Management versions from 5.12 up to 5.17. When a local method is called within a Groovy script with a hyphen, Groovy generates an invalid class name, causing a silent failure and affecting the automation processes.
To resolve this issue, rename your script files to not include hyphens. You can use camelCase or underscores _ instead. For example, if your script is named some-test-script.groovy, rename it to someTestScript.groovy or some_test_script.groovy. For more information, go to the following Jira issue:
JSDSERVER-15647 - Getting issue details... STATUS
We’ve addressed this issue in Jira Service Management 10.0 and later by upgrading groovy-all from 2.4.15 to 4.x. More about upgrading to Groovy 4
End of support announcements
There are no changes to supported platforms in this release.
For the list of supported platforms, check Supported platforms.
For previous announcements, see End of support announcements.
App developers
For any important changes regarding apps, check out the Jira changelog.
Upgrade procedure
To help you upgrade to the latest and greatest:
- See Upgrading Jira applications for complete upgrade procedures, including all available upgrade methods and pre-upgrade steps.
- For a more tailored upgrade, go to Jira administration > Applications > Plan your upgrade. We’ll recommend a version to upgrade to, run pre-upgrade checks, and provide you with a custom upgrade guide with step-by-step instructions.