Jira Service Management 4.17.x upgrade notes
Below are some important notes on upgrading to Jira Service Management 4.17. For details on the new features and improvements in this release, see:
Here's some important information you should know about:
Security advice: Allowing customers to raise requests
We’ve published a security advice regarding the setting “Anyone can email the service project or raise a request in the portal” that can be set in Administration > Applications > Jira Service Management configuration. If you’re using this setting, make sure to read it. For more info, see Managing access to your service project.
Excluding custom fields from data pipeline exports
User-generated custom fields and fields provided by apps are now included in the data pipeline export by default. If you want to exclude custom field data, set the data.pipeline.feature.jira.all.exportable.custom.fields.disabled dark feature flag.
Connecting Jira to Microsoft SQL Server 2019
You can now use Microsoft SQL Server 2019 as your database. For more info on how to connect Jira to this database, see Connecting Jira application to SQL Server 2019.
Removing obsolete JIM importers
We’ve removed obsolete importers deprecated in Jira 8.4, and they are no longer available. From now on, you can only use the CSV and JSON importers. Importers provided by 3rd party app aren’t affected by this change.
FogBugz On Demand
Upgrading Insight - Asset Management
Insight - Asset Management has been part of Jira Service Management Data Center since version 4.15. When you upgrade to the new version, Insight will be upgraded automatically without any issues. However, if you were using this app on earlier versions (or if you're using an equivalent Insight app from Marketplace), you might need to complete some pre-upgrade steps.
For more info about the steps, see Upgrading Insight with Jira Service Management.
End of support announcements
Here are the changes to supported platforms in this version:
- Deprecating PostgreSQL 9.6: We're deprecating PostgreSQL 9.6, and plan to remove it in Jira Service Management 4.19.
Deprecating Microsoft Edge Legacy: After introducing support for Microsoft Edge (Chromium), we’re deprecating Microsoft Edge Legacy, but you can still use it with this version.
For the list of supported platforms, see Supported platforms.
See Preparing for Jira 8.17 for any important changes regarding apps.
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.