✓ OAuth 2.0 for your incoming mail
✓ User anonymization (GDPR) improvements
✓ More insight into your custom fields
✓ Stale nodes automatically removed
✓ Optimized custom fields
OAuth 2.0 for your mail server
SERVER DATA CENTER
Given that Google and Microsoft are planning to disable Basic Authentication, Atlassian wants to ensure that you can still enter your comments into Jira and create issues via email. OAuth 2.0 support will be added so you can use it as an authentication method for Gmail or Microsoft Exchange online instead of using a password.
Create your OAuth integration, then update your inbox server and leave the rest to the Atlassian team. This will ensure that the connection to your mail server works seamlessly.
User anonymization (GDPR) improvements
SERVER DATA CENTER
Already in Jira 8.7, Atlassian introduced user anonymization to help you comply with DSGVO regulations. The initial feature came with some limitations, which they continue to fix in newer versions. In this release, the scope of anonymization has been expanded to include the following:
- 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 this case Atlassian will take care of the newly supported elements and make your users disappear in a breath of GDPR.
More insight into your custom fields
If you have ever wondered which of your custom fields makes indexing by Jira difficult, Atlassian has the answer. No need to dig through the logs, the information is now easily accessible. The custom field indexing page created there shows you the 10 fields that take the longest to index, so you can analyze the instance and take action. This is especially useful in enterprise environments, as custom fields can sometimes be challenging.
To view the information, go to Jira Administration > System > Clustering > Actions > Indexing Custom Fields.
Stale nodes automatically removed
Atlassian has already introduced the automation of your cluster maintenance. Now you no longer need to manually remove the offline nodes from your cluster or move the nodes that do not report a heartbeat offline. If a node reports no movement for two days, it is automatically moved to offline state, and if it remains offline for two days, it is automatically removed from the cluster.
In addition, Atlassian gives you a complete overview of what is going on in your cluster in your extended audit log. This way you know immediately when a node goes offline or is removed from the cluster, and thus what is going on in your cluster.
Optimized custom fields
A large number of user-defined fields can have a negative impact on performance and indexing time in Jira. To minimize these effects, a new optimization is introduced that reduces the number of called field indexers.
Now Atlassian will not store sort marks for custom fields if no values are available for a particular problem. In addition, indexers will only run if custom field values exist for a particular problem, the custom field is visible, and an application area has been assigned to that problem.