Jira Software 8.2.x release notes
21 May 2019We're pleased to present Jira Software 8.2.
Interested in trying a shiny new version? Don't forget to renew your active software maintenance! Renew now.
If you're looking for compatible Jira applications, look no further:
Sneak peek into Jira's roadmap
If you want to know when our next Enterprise release is coming, see: Next Jira Enterprise release.
Filters to limit the number of archived issues you export
As a sys admin you can export your archived issues to a CSV file. However, we want to make sure this file is readable and useful to you. That is why we've introduced filters which help you limit the number of archived issues you export, and as a result, the size of the file. Now, you can select to export archived issues from a selected project or decide on the number of archived issues to go into the CSV file.
For detail on how to archive issues, see Archiving an issue.
New colors of issue statuses
To bring more consistency between the Jira Server and Jira Cloud applications, and to move another step closer to the new Atlassian Design direction, we’ve updated the colors of issue statuses. Now, when working with your issues and moving them around, you’ll see the following changes:
Support for Java 11
Following on our promise to add support for Java 11, we’re happy to announce that it’s finally here! Java SE 11 is the latest Long-Term-Support release, so you’ll be able to get updates and fixes for longer. Learn more about our plans regarding Java
Support for Microsoft SQL Server 2017
We're welcoming another supported database to our family—Microsoft SQL Server 2017. Learn more
Updating apps has never been easier
We’ve fixed several issues that caused performance degradation in large Jira instances when installing or updating the Marketplace apps. Until now, every update of an app could make Jira slow down or even freeze for some time. If you’ve encountered this problem before, it’s way better now, so feel free to update your apps anytime. You can read more about this fix here.
Exporting all the issues you need
To avoid memory problems, Jira had a default limit of 1000 when exporting issues to CSV. Though we’ve decided to keep the default limit in place, we’ve reduced the amount of memory needed during the export so you can increase the limit and export more issues in one go. In our tests, exporting 100K issues (each with 10 custom field values) required 57MB of memory compared to almost 2GB before this change. You can read more about this fix here.
You can safely increase the limit, but keep in mind that many big exports will still affect Jira performance. To change the limit, have a look at Jira advanced settings.