We’ve just released the first EAP for Jira 8.19 (Data Center & Center).
Upgraded dependencies and libraries
We’ve published a list of dependencies and libraries upgraded in this version. We’ll keep updating it as we release next EAPs.
Changes in the Reindex(issue) API
The Reindex (Issue) API was supposed to reindex only the issue, but it was also reindexing all the comments and work history along with the issue. Now we are correcting it to reindex only the issue.
Java 11 is now bundled in our binary installers
Jira 8.19 binary installers come bundled with the AdoptOpenJDK 11 JRE. If you plan to install Jira manually from a
.ziparchive, you can continue to use Java 8 or switch to Java 11.
Changes to the H2 Database Engine JDBC connection string
If Jira is set up with the H2 Database Engine for evaluation purposes, the
dbconfig.xmlwill now use the
jdbc:h2:retryconnection string prefix instead of
Support for PostgreSQL 12 and Amazon Aurora PostgreSQL 10
Jira 8.19 adds support for PostgreSQL 12 (Server and Data Center) and Amazon Aurora PostgreSQL 10 (Data Center only).
End of support for PostgreSQL 9.6
As of Jira 8.19, support for PostgreSQL 9.6 is dropped.
Adding approvers from Insight objects (Data Center)
We’ve added a new way to add approvers to your requests. Instead of using a regular user-picker field with approvers, you can now also use the Insight custom field that adds approvers who have some relations to the objects (assets) selected in your requests.
More languages in Insight - Asset Management
We’ll be adding new languages to Insight - Asset Management, both the built-in functionality in Jira Service Management and the separate Marketplace app.
Multiple email channels for creating requests (Data Center)
This is planned to be released in one of the future releases, not JSM 4.19.
We’re working on increasing the number of email channels you can configure in Jira Service Management so your customers can send emails to different addresses and get them turned into requests or comments. This will let you use different channels for different request types, or just have more personalized email addresses for your customers.
If you have any comments, just post them below.
The Jira team