Preparing for Jira 8.18
This documentation is intended for Jira developers who want to ensure that their existing apps are compatible with Jira 8.18.
Quick info
Latest version
Here you can find information about the latest EAPs.
| Application / Date | EAP number | Version (Maven) | Downloads |
|---|---|---|---|
Jira Core/Software | 8.18.0-RC01 | 8.18.0-m0003 | Source files (Core) Source files (Software) |
Jira Service Management | 4.18.0-RC01 | 4.18.0-m0003 |
Summary of changes
In this section we'll provide an overview of the changes we intend to make, so you can start thinking how it might impact your apps. Once they're ready, we'll indicate when a change has been implemented, and in which milestone.
Upgraded dependencies and libraries
Status: IN PROGRESS
As announced in this post about security uplift, we’re putting more focus on upgrading core components and libraries in Jira to improve security. Here’s a list of libraries that we’ve already upgraded. We’ll update it as we release new EAPs:
Jira Core/platform
| Library/dependency/change | Source version | Target version | Important notes |
|---|---|---|---|
| Guava | 26.0-jre | 30.1.1-jre | - |
| H2 Database Engine | 1.4.185 | 1.4.200 | The new version breaks compatibility with database files created by version 1.4.185. |
| Java Servlet API | 3.0.1 | 3.1.0 | - |
Jira Software
| Library/dependency/change | Source version | Target version | Important notes |
|---|---|---|---|
org.eclipse.jgit:org.eclipse.jgit | 2.2.0.201212191850-r | 5.11.0.202103091610- | - |
| deep-extend | 0.4.2 | 0.6.0 | - |
Jira Service Management
| Library/dependency/change | Source version | Target version | Important notes |
|---|---|---|---|
Fixed ability to bypass filter against Prototype Pollution. | - | - | - |
Other plugins
| Plugin | Library/dependency/change | Source version | Target version | Important notes |
|---|---|---|---|---|
| Jira Autolink plugin | com.atlassian.pom:closedsource-pom | 3.0.87 | 5.0.29 | - |
| All Jira Core dependencies | 7.0.0 | 8.17.0-QR-20210415072638 | - | |
| dom4j:dom4j (from com.atlassian.jira:jira-api) | - | - | Excluded | |
| Jira Inform plugin | All Spring libraries | 4.2.5.RELEASE | 5.1.18.RELEASE | - |
| Active Objects | 1.5.0 | 3.2.11 | - | |
| Jira Importers plugin | org.codehaus.jackson | * | 1.9.13-atlassian-5 | - |
Some transitive dependencies from Jira API, Jira Core, and Jira Service Management have been excluded. | - | - | Excluded. Please check the source files for details if you're using this plugin. | |
| Jira REST Java client | Platform version | 3.1.7 | 5.2.1 | - |
| Atlassian HTTPClient | 2.0.0 | 2.1.4 | - | |
| commons-io:commons-io | 2.1 | 2.8.0 | - | |
| log4j:log4j | * | 1.2.17-atlassian-3 | - | |
| com.atlassian.fugue:fugue | - | - | Removed |
Upcoming bugfix releases
Our bugfix releases follow a predefined, monthly schedule. This makes it easier for you to plan your next upgrade. New bugfix versions are released for three Jira feature versions: Latest version, Jira 8.13 LTS, and Jira 8.5 LTS. We may occasionally skip a bugfix release if it isn’t needed. All bugfix releases include security and regular bug fixes.
Estimated release timeframes
- 14-21 June, 2021
- 12-19 July, 2021
- 16-23 August, 2021
Comments reactions in Jira (Data Center)
App: JIRA SOFTWARE
Status: IMPLEMENTED (eap 01)
We continue improving Jira commenting experience. As of this release you can use reactions to comments posted in issues. Use emojis to express interest, provide feedback, or speed up the approval process.
This feature is enabled by default. To disable it, go to System > Edit Settings > Enable emoji reactions and switch the toggle.
Multiple email channels for creating requests (Data Center)
App: JIRA SERVICE MANAGEMENT
Status: IN PROGRESS (eap 01)
This is planned to be released in one of the future releases, not JSM 4.18.
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.
In this EAP (and the upcoming JSM 4.18 release), we're sharing our work in progress on this feature. You can already test it and give us feedback on the improvements you'd like to see. This feature is planned for one of the upcoming releases of Jira Service Management.
To enable and test this feature, see Adding multiple channels for creating requests.
To share your feedback, take this survey.
SLAs on customer portals (Data Center)
App: JIRA SERVICE MANAGEMENT
Status: IMPLEMENTED (eap 01)
You can now choose to display SLAs for your customers on customer portals.
Enabling SLAs on portals
When creating or editing an existing SLA, you will see an option to show it in the customer portal.
Viewing SLAs on portals
When enabled, SLAs will be displayed for customers in a similar way as for agents.
Layout changes
We’ve migrated the SLA component to React.js, so you might want to test your app with the new layout. The new layout will be available both in the agent view and customer portal, here’s some examples of how SLAs look now:
| Type | Current | New |
|---|---|---|
| At risk, time remaining |
|
|
| Paused, on track |
|
|
| Running, on track |
|
|
API changes
There are no new REST APIs, but we added a new (optional) customerVisible boolean JSON to the data type returned by SLA endpoints APIs.
When you omit this flag in the CREATE SLA request, the SLA won’t be shown on the customer portal.
When you omit it in the UPDATE SLA request, the SLA will keep its original setting.
Disabling the search bar on customer portals (Data Center)
App: JIRA SERVICE MANAGEMENT
Status: IMPLEMENTED (eap 01)
Many of our users aren't linking a Confluence knowledge base to their service projects and find the default search bar not needed or even confusing. That's why we've now added an option to disable the search bar.
To disable the search bar for a project:
- Open your project.
- Go to Project settings > Portal settings.
- In the Search section, disable the search bar.
Here's what a customer portal looks like with the search bar disabled:
Good to know
- The search bar can only be disabled for a project's customer portal. It can't be disabled for the main help center.
- When you disable the search bar and you have the Confluence knowledge base linked, we'll notify you, just in case you disabled it by mistake.
Mentioning users on customer portals
App: JIRA SERVICE MANAGEMENT
Status: IMPLEMENTED (eap 01)
Mentions are a great way to collaborate with your teammates, but they were never available on customer portals. Now, you can mention users in comments and issue descriptions in the same way as you would mention them in Jira, for example by typing @captainjoe.
Good to know
- When you mention a user on a request, they will be added as Request participant.
- When a user has an account in Jira (non-customer), they will get a duplicate notification about being mentioned: one from the Jira mail, and one from Jira Service Management customer notifications.
Who can mention whom?
There are certain restriction on whom you can mention, depending on permissions:
- Admins and agents can mention anyone in the project
- Customers can only mentions customers from their organization
- If the Any customer or organisation, by searching in this project option is enabled, then customers can also mention anyone in the project