Jira Service Management 4.22.x upgrade notes
Below are some important notes on upgrading to Jira Service Management 4.22.x. For details on the new features and improvements in this release, see:
Changes coming with OAuth 2.0
As mentioned in the release notes, you can now configure Jira as an OAuth 2.0 provider. This brings the following changes:
Current OAuth 2.0 client integrations
You could already configure Jira as an OAuth 2.0 client, which you probably did when configuring your mail servers. You can no longer find these integrations in Administration > OAuth 2.0. We’ve moved them to Administration > Application links. No action is required on your side.
Configuring Jira as an OAuth 2.0 provider
If you’d like to switch to using OAuth 2.0, you’ll most likely need to update your current integrations that use OAuth 1.0 or build new ones, compatible with Jira. To understand what OAuth 2.0 flows are available and what data you need, see the details of our OAuth 2.0 provider implementation in Jira OAuth 2.0 provider API.
If your integrations are ready to go, here you can learn how to use them in Jira: Link to other applications.
Support for Microsoft GCC accounts
You can now select a Microsoft GCC email address to receive email request in your Jira Service Management project. Learn more about receiving email requests
End of support announcements
For the list of supported platforms, see Supported platforms.
See Preparing for Jira 8.22 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.