Jira Service Management 5.15.x upgrade notes
Below are some important notes on upgrading to Jira Service Management 5.15.x. For details on the new features and improvements in this release, see:
Upgrade notes
Encrypted credentials will be re-encrypted on upgrade
We streamlined the way in which credentials are encrypted across Jira Service Management. When you upgrade, saved credentials (such as email channels, Opsgenie, and Confluence Cloud API keys) will be re-encrypted using the new cipher library.
This change will not affect your upgrade process. In case you run into any issues, re-enter the credentials. This will re-encrypt the credentials before they are saved to the database.
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
New location of the backup export directory
As of Jira Software 9.15.0, the default backup export directory has been changed from <jira-home-dir>/export to <jira-home-dir>/export/backups, where <jira-home-dir> is your Jira [shared] home directory. The export directory is now a general purpose directory used by data pipelines and support zips.
More about important directories and files
Amazon S3 storage configuration updates
BUGFIX RELEASE 5.15.1
We’ve changed the Amazon S3 client to the CRT-based asynchronous version. Also, in bugfix release 5.15.1, we've added a new optional parameter max-concurrency to filestore-config to allow configuring the number of simultaneous threads used for read and write operations. Check out how to use max-concurrency.
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
Check out the Jira Data Center changelog for any important changes regarding apps.
Known issues
This section contains information about any issues that we’ve discovered in our testing. We’re constantly keeping an eye out and if we find anything, we’ll let you know right here.
Random values are added to the Assets custom field
Jira Service Management 5.15.0 and 5.15.1 are affected by a bug, which causes random values to appear in the Assets custom field. We're working on fixing this issue in an upcoming bufgix release. More information about this issue is available under the following link:
JSDSERVER-15255 - Getting issue details... STATUS
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.