Jira Core 9.2.x release notes
We're pleased to present Jira Core 9.2.
Upgrading from 8.x to 9.x triggers full Jira reindex that causes some downtime during the process. If you’re on 8.x now, make sure you’ve estimated the downtime and set the best time for the upgrade.
Learn more about how to handle full reindex and estimate downtime
More
Read the upgrade notes for important info about this release and see the full list of issues resolved.
Compatible applications
If you're looking for compatible Jira applications, look no further:
Good to know
If you're thinking to move to Data Center, check our recommendations first. See: Infrastructure recommendations for Jira.
Jira agile views: faster loading, better performance
We've always been laser-focused on Jira performance improvements and this release comes with yet another update. This time, we've optimized page load times for Jira Backlog and Board agile views.
As the app gets faster and more reliable, you can get more out of your work in Jira, specifically if you're dealing with slow-performant hardware or network issues. This change is just a part of our planned performance enhancements so expect more to come in the upcoming releases.
Interested in technical details behind this update? We have it covered in the Preparing for Jira 9.2 notes, just take a minute to check it out.
Introducing OAuth 2.0 for outgoing mail
We’ve enabled OAuth 2.0 authorization for outgoing mail servers. Google and Microsoft are still supported as providers along with the SMTP protocol available for connection. So, now, you can set up both your incoming and outcoming mail servers to use OAuth 2.0, providing tight security around Jira integrations and connections with third-party apps.
In the configuration for your outgoing mail, you can choose from available authentication methods, which depend on your provider, or enable the use of a JNDI location. When the configuration is ready, you can test the connection before applying the changes.
The feature is active by default. But if needed, you can continue using your current outgoing mail configuration.
Learn more about SMTP mail server configuration
Jira pickers get a performance boost
Ready for another portion of performance-related changes? Meet one more set of improvements in Jira pickers.
Further to project picker updates introduced in Jira 8.21, we’ve optimized a few more dropdown menus in the app: Component, Priority, and Version pickers in the basic search mode. More than that, working with pickers when creating or editing an issue got much faster as well. You can now be sure that your app performance won’t be affected by a growing number of elements to render.
Wondering what’s changed in particular?
We’ve revamped the way search results are rendered: instead of initially loading all the available items for a particular picker, we now only display 100 items on the list. We query the backend as you type, returning exactly what you’re looking for.
You can also use newly added API endpoints to query versions, components, issue types, resolutions, statuses, and priorities. These endpoints return paginated results to limit the response size of potentially large collections of items.
Parameters
Name | Type | Is mandatory? | Description |
|
| OPTIONAL | A sequence of characters expected to be found in status names. When no value is provided, all statuses will be returned. |
|
| OPTIONAL | Indicates which status should be used as the first item in the page of results. The default value is |
|
| OPTIONAL | Indicates how many statuses will return per page. The default value is |
|
| OPTIONAL | A list of issue type IDs to further restrict the search. When provided, only statuses available in given issue types will be returned. |
|
| OPTIONAL | A list of project IDs to further restrict the search. When provided, only statuses available in given projects will be returned. |
Sample request
GET http://<sample instance>/rest/api/2/status/page?query=Do
Sample response
Configuring diagnostic recording with JFR
We’ve added the ability to configure diagnostic recording via the user interface and REST endpoints with Java Flight Recorder (JFR). Now, to get the desired information, you can configure the amount of recorded data to simplify and improve problem diagnostics.
To do this, you can adjust the following JFR settings:
- Maximum recording age
- Maximum recording size
- Thread dumps recording interval
By playing with these settings, you get the power to boost troubleshooting on your instance and, as a result, fix problems faster and more effectively.
Learn more about how to use Java Flight Recorder