Jira Software 8.10.x release notes
23 June 2020
We're pleased to present Jira Software 8.10.
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:
If you're thinking to move to Data Center, check our recommendations first. See: Infrastructure recommendations for Jira.
Our Jira Pro Tip for this release
Need a tailored upgrade path? Check out our Pre-upgrade planning tool. Learn more...
OAuth 2.0 for your mail server
SERVER DATA CENTER
With Google and Microsoft planning to disable Basic Authentication, we want to make sure you can still add your comments to Jira and create issues using email. We're adding OAuth 2.0 support so that you can use it as an authentication method for Gmail or Microsoft Exchange online instead of password.
Create your OAuth integration, then update your incoming mail server and leave the rest to us. We'll make sure the connection with your mail server works seamlessly. Learn more
User anonymization (GDPR) improvements
SERVER DATA CENTER
Back in Jira 8.7, we introduced user anonymization to help you stay compliant with GDPR. The initial feature came with some limitations that we continue to fix in newer versions. In this release, we have extended the scope of anonymization to include the following items:
Reporters and creators of issue collectors
Full name in the issue history (Assignee, Reporter, Single- and Multi-user picker fields)
- Ability to anonymize users that have already been deleted
If you have already anonymized some users, you can anonymize them again, in which case we’ll take care of the newly supported items and make your users disappear in a puff of GDPR. Learn more
More insight into your custom fields
If you're ever wondered which of your custom fields makes Jira indexing a drag, we can show you the culprit. No need to dig in the logs, because the information is now easily accessible. The Custom field indexing page we've created shows you top 10 fields that take the longest to index allowing you to analyse the instance and take action. This is especially helpful in enterprise environments as custom fields can sometimes be challenging at scale.
To view the information, go to Jira Administration > System > Clustering > Actions > Custom field indexing. Learn more
Stale nodes automatically removed
We've introduced automation to your cluster maintenance. Now, you do not have to remove the offline nodes from your cluster manually, or move the nodes that report no heartbeat offline. After two days of a node reporting no heartbeat it's automatically moved offline, and after two days of remaining in the offline state, it's automatically removed from the cluster.
Additionally, we give you a full overview of what is going on in your cluster in your Advanced audit log. This way, if a node goes offline or is removed from cluster you know it in an instant. Learn more
Optimized custom fields
Large number of custom fields can negatively impact performance and indexing time in Jira. To minimise this impact, we’re introducing a new optimization that reduces the number of called field indexers.
Now, we won’t be storing sorting markers for custom fields when values don’t exist for a particular issue. Additionally, indexers will be executed only when custom field's values exist for a particular issue and the custom field is visible and has scope scope assigned for that issue. Learn more
Issues resolved in 8.10.0
Released on 23 June 2020
Issues resolved in 8.10.1
Released on 20 July 2020
Was this helpful?Yes Provide feedback about this article