We’ve just released the first EAP of Jira 8.14 (Data Center & Server). Here are the highlights of this release:
Improvements to email templates (Data Center)
We’ve added a new page to the Jira administration where you can download all your email templates and upload them back after editing. We’ll also move the templates to your Jira shared home directory so you don’t have to modify them with every upgrade.
DVCS Connector improvements
We’ve added a number of improvements to the DVCS Connector that is bundled with Jira. The most prominent ones are performance improvements, which should help with managing all these DVCS accounts, and support for GitLab.
Personal access tokens
The Jira REST API provides endless opportunities for automation and integration with other systems. For extra peace of mind, you can now create personal access tokens, which are a safe alternative to using a username and password for authentication.
Embedded Crowd and password encryption
We’ve upgraded Embedded Crowd, which gives you access to some of the Crowd 4.2 features inside of Jira. An important one is the ability to encrypt database passwords to external user directories, also in your backups.
Setting context while creating custom fields
We’ve added an option to set the context while creating a custom field. This should help you limit the number of custom fields with global context that can affect Jira’s performance.
Issues in epic displayed in the detail view
We’ve added the “Issues in epic” section to the detail view. Until now, it was only available after opening an epic. This change applies only to Kanban boards where you can choose to show epics as cards.
Passing credentials via URL parameters no longer possible
We’ll be blocking the default possibility to log into Jira by passing credentials via URL parameters.
Jira Service Desk is now Jira Service Management
This change emphasizes our move into the ITSM area, with new features like incident management, mobile support, and improvements to agent queues. We also have some exciting plans for the future.
If you have any comments, just post them below.
The Jira team