seen from Germany
seen from China
seen from United Kingdom
seen from United States
seen from Canada
seen from United States
seen from Germany
seen from Malaysia
seen from Mexico
seen from United States
seen from Italy
seen from United States
seen from Germany
seen from Germany
seen from South Africa
seen from United States
seen from Germany
seen from Malaysia
seen from United States
seen from Guernsey
EAP - Jira 8.4.0-EAP03 Release Notes
To help you navigate between pages, you can go directly from a link, for example in an email notification, to the app. If you do not have the app yet, clicking the link will take you to the app download page in Play store (only for Android). Simply click the Open in app button that displays in mobile web.
Source
EAP - Jira 8.4.0-EAP01 Release Notes
This documentation is intended for Jira developers who want to ensure that their existing apps are compatible with Jira 8.4.
Upcoming releases
EAP 02 planned for August 13th
Summary of changes
In this section we'll provide an overview of the changes we intend to make in Jira 8.3, 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.
Deprecation of Jira native importers
Status: IMPLEMENTED (EAP 01)
We have dropped support for several native importers that used to be available as part of Jira Importers Plugin (JIM). As of JIRA 8.4 we're only supporting import from CSV and JSON.
Filters to browse archived issues
Status: IMPLEMENTED (EAP 01)
Now, if you open your list of archived issues in Issues > Archived issues, you can browse archived issues using a selection of filters. In this way, you can quickly find the issues you need. You can filter your issues by, for example, Reporter, Archive date, or Archiver.
To be able to browse archived issues, you need the Browse Archive or the Browse Project Archive permission.
Additionally, system admins can easily export archived issues to a CSV file.
Jira becomes more accessible and clear
Status: IMPLEMENTED (EAP 01)
To improve the accessibility in Jira and respond to the needs of the motor and visually-impaired users, we've fixed color contrast in buttons and messages, added labels for UI elements to be picked up by screen readers and made sure you can add comments with a keyboard shortcut.
AUI upgraded to version 8.4
Status: IMPLEMENTED (EAP 01)
We've upgraded AUI version 8.4 and as a result improved the readability of form fields, changed the form and focus styles, and lozenge colors. Also we've changed layering that affects dropdowns.
You can see some of the changes below:
Before 8.4
Jira 8.4
We do not expect the changes to cause issues however, if you need to disable them, do the following:
on the form level, add the aui-legacy-forms CSS class to the <form> element (in case of any issues with form and focus styles)
on the page level, add the aui-legacy-focus CSS class to the <body> element (in case of any issues with focus styles).
The public-facing HTML and JS APIs of AUI components have remained unchanged.
createmeta REST endpoint will soon be removed
Status: IMPLEMENTED (EAP 01)
This endpoint is commonly used when Atlassian products are integrated to create issues in Jira from a Confluence, Fisheye, or Bitbucket instance. However, /jira/rest/api/2/issue/createmeta?params has been reported to cause issues especially on larger instances. That is why we decided to remove this endpoint in Jira 9.0. In Jira 8.4 we'll make other calls available to mitigate the issue. Read more...
Better support for reply emails from Outlook by mailhandlers
Status: IN PROGRESS (planned for EAP 02)
To help the users of Outlook be able to respond to Jira notifications, we have improved the RegexCommentHandler UI to make it easier to set it up properly, and are advising admins not to use the NonQuotedCommentHandler as it does not work with html or rich text emails. In this way, admins can set up the handlers in such a way that when users comment in Jira via email, signature text or attachments are removed and are not added to the Jira content.
We are also planning to deprecate the ”Add a comment from the non-quoted email body” and ”Create a new issue or add a comment to an existing issue” email handlers in the foreseeable future. For more information, see Jira and Outlook.
External links open in a new tab
Status: IMPLEMENTED (EAP 01)
Now, you do not need to right-click every time you want an external link that's added to a Jira issue want to open in a new tab in your browser. We've made this option default for external links. However, if you like all links to open in the same tab, you can easily change this in YourUserProfile> Profile > User Preferences > External link.
Batching emails will be a default setting
Status: IMPLEMENTED (EAP 01)
As of Jira 8.4, email notifications will be batched by default. This will save you a lot of space in your email box. However, if you want your notifications to arrive separately, you can still disable the feature. Also, the feature will remain disabled if you disabled it in a previous version of Jira. For more information on how batching works, see Configuring email notifications.
Generating user keys becomes default
Status: IMPLEMENTED (EAP 01)
We have introduced a new way of generating user keys for new users. The reason behind it is that we want to reduce the number of places where we store users’ personal data.
Up to now, the user key has been the same as username, lowercased. For example, user Admin got a user key admin. If there’s been a naming conflict, the user key has been set to a value like ID10100.
We’re now changing this approach so that all user keys for new users (no changes for existing users) have the following format: JIRAUSER10100. This approach becomes the default in Jira 8.4 and is no longer a dark feature.
Filters in Multi User picker Custom field
Status: IMPLEMENTED (EAP 01)
We've added the option to select multiple users in the limited user picker. Now, you can limit the multi user picker custom fields to hold only specific set of users.
A large number of versions no longer breaks boards
Status: IMPLEMENTED (EAP 01)
Now, even if you have a large number of open version, your Jira is safe and no boards get broken.
Aurora support for Data Center
Status: IN PROGRESS (planned for EAP 02)
As of 8.4, we'll start supporting the Aurora database in Jira DC. To test this database with the EAP, you need to deploy an Aurora DB and switch to it manually. For information on how to do it, refer to the AWS Quick Start for deploying a stand-alone Aurora DB: https://aws-quickstart.s3.amazonaws.com/quickstart-amazon-aurora/doc/modular-architecture-for-aurora-postgresql-on-the-aws-cloud.pdf
Source
EAP - Jira 8.3.0-EAP02 Release Notes
Support for Oracle 12c Release 2
We have introduced support for Oracle 12c Release 2 database, which remains under Oracle's Premier Support.
GDPR changes in JIRA - new API
To improve the compliance of Jira Server with General Data Protection Regulation (GDPR), we'll be introducing a set of changes in Jira over the next few months.
Now, we are we’re implementing an API for disabling users who leave the company and an API for user anonymization. This will save time and workload for enterprise admins and allow admins to automate processes.
atlassian-jslibs bumped to 1.4.1
We have upgraded the atlassian-jslibs plugin from version 1.2.5 to 1.4.1 and are now bundling React 16.8.6 , ReactDOM 16.8.6 factory, and Marionette 4.1.2 with Jira.
We've also upgraded the Browse projects page to the latest version of Marionette, which gave it a significant performance boost.
List of custom changes after upgrade
This change is a part of a bigger project to help you plan and speed up your upgrade. In the planning phase, you can already see the changed files in the Pre-upgrade planning page in the Administration > System > General configuration. This can hep you estimate the time required to transfer the changes and make sure none have been lost. When you transfer the changes from the old to the new files, remember to only copy these exact changed parts not the entire files.
New filters to search for custom fields
Now, you can find a custom field even if you do not know its exact name. You can use one or a collection of the additional three multi-select filters and search through your custom fields based on
projects using custom field
custom field types
screens connected to a custom field
Source
EAP - Jira 8.3.0-EAP03 Release Notes
No publicly available changelog for this release
Source
EAP - Jira 8.2.0-EAP01 Release Notes
This documentation is intended for Jira developers who want to ensure that their existing apps are compatible with Jira 8.2.
Quick info
EAP 1 is not available yet, but we're planning to release it soon. In the meantime, you can review the planned changes described on this page.
All changes and EAPs
Below, you can see the summary of changes, and more details about them organized by the EAP they've been implemented in.
Summary of changes
Implemented changes
EAP 1 - coming soon
Summary of changes
In this section we'll provide an overview of the changes we intend to make in Jira 8.2, 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.
GDPR changes in Jira
Status: ONGOING (for details, see GDPR changes in Jira)
To improve the compliance of Jira Server with General Data Protection Regulation (GDPR), we'll be introducing a set of changes in Jira over the next few months. The first changes will be available to test in EAP 1, so we can gather your feedback and refine them.
CDN for Jira Data Center
Status: PLANNED
We're currently working on adding the ability to serve static assets from a CDN in Jira Data Center.
In Jira 7.0 we moved to stateless delivery of JavaScript and CSS resources. Apps that don't use the new APIs for web-resource transforms and conditions may cause static assets to be cached incorrectly, when CDN is enabled. See Stateless web-resource transforms and conditions to make sure your app is using the new APIs for web-resource transforms and conditions.
We will also provide a health check on the CDN administration screen that will indicate if an app is using deprecated methods.
These changes will not be included in Jira 8.2, but we're planning to add them in one of the next releases.
Microsoft SQL Server 2017
Status: PLANNED
We're currently working on adding Microsoft SQL Server 2017 to the list of supported databases.
Support for Java 11
Status: IMPLEMENTED
In addition to OpenJDK 8 and Oracle JDK 8, we will officially support running Jira on OpenJDK 11 and Oracle JDK 11. However, we still encourage the apps to be developed using Java 8 to ensure Java 8 compatibility and tested on both Java 8 and Java 11.
AdoptOpenJDK 8 bundled with Jira
Status: IMPLEMENTED
Jira is no longer bundled with Oracle JDK and comes with AdoptOpenJDK 8 instead. This applies only to Jira installers. If you're using archives, you need to install Java separately.
Polyfills in Jira
Status: IMPLEMENTED (for details, see Polyfills in Jira)
Jira 8.2 will be supporting new APIs, so you can use the EcmaScript language features and Browser runtime features without the need for providing your own runtime polyfills.
Changes to issue cards in backlogs
Status: IMPLEMENTED (for details, see EAP 1)
We’ve made small changes to issue cards displayed in backlogs to better handle long issue names. If the issue name can’t fit into the issue card, it’ll end with an ellipsis.
Implemented changes
EAP 1
Release date: not available yet
Changes in this milestone
GDPR changes in Jira
This milestone contains the first changes related to the GDPR project:
Anonymizing users: new extension points that will notify your app when a Jira admin decides to anonymize a user.
Generating user keys: new way of generating user keys (hidden behind a dark feature flag) to reduce the amount of personal data we store in Jira.
For more info on these changes and the GDPR project in general, see GDPR changes in Jira.
Polyfills in Jira
Jira 8.2 will be supporting new APIs, so you can use the EcmaScript language features and Browser runtime features without the need for providing your own runtime polyfills. For details, see Polyfills in Jira.
Changes to issue cards in backlogs
We’ve made small changes to issue cards displayed in backlogs to better handle long issue names. If the issue name can’t fit into the issue card, it’ll end with an ellipsis, like in the following example:
Changes that might be interesting:
We've removed the following wrapper:
<div class=“ghx-end ghx-row ghx-row-version-epic-subtasks”></div>
The content remains the same, but it no longer contains the <div> wrapper. We’ve removed it so we could make all elements included in an issue card display on one level and identify where the issue name ends.
We've removed the following that controls the element displaying the user avatar and estimate:
<span class=“ghx-end ghx-extra-field-estimate”>
Now, this element will aways use the following class (previously, it could use either of the two):
<span class=“ghx-end ghx-estimate”>
Source
EAP - Jira 8.1.0-EAP02 Release Notes
There are no significant changes in this milestone.
Source
EAP - JIRA 8.1.0-EAP01 Release Notes
This documentation is intended for Jira developers who want to ensure that their existing apps are compatible with Jira 8.1.
All changes and EAPs
Below, you can see the summary of changes, and more details about them organized by the EAP they've been implemented in.
Summary of changes
Implemented changes
EAP 1 - 5 March 2019
Summary of changes
In this section we'll provide an overview of the changes we intend to make in Jira 8.1, 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.
Deprecating 32-bit installers
Status: PLANNED
We are considering only providing 64-bit installers for Jira, and deprecating the 32-bit ones. Users who need to stay on 32-bit systems will be able to install Jira by using the zip/tar.gzarchives. The 32-bit installers will not be removed in Jira 8.1, but they might be deprecated in this version, and then removed in Jira 8.2.
Batched email notifications: improvements
Status: PLANNED
We'll be improving batched email notifications by removing a limitation that didn't allow to use custom fields in emails. Custom fields will be supported, but we'll still keep this feature disabled by default. This will probably change in the next releases, as we want notifications to be batched by default eventually.
'Issue details' panel is resizable on Scrum/Kanban boards
Status: IMPLEMENTED (for details, see EAP 1)
Until now, users could manually resize the 'Issue details' panel only on Scrum/Kanban backlogs (you can check how it works there). After receiving many requests, we've also added this possibility to Scrum/Kanban boards. Additionally, we've added a horizontal scrollbar for boards that have many columns and are displayed on small screens.
Column headers limited to 1 line
Status: IMPLEMENTED (for details, see EAP 1)
This change will be released in Jira 8.0.2, just making sure you know about it.
Column headers will be limited to one line, containing the column name (shortened with ellipsis), and column constraints (min. and max. issues, if enabled). For details, see EAP 1.
New avatars
Status: IMPLEMENTED (for details, see EAP 1)
This change will be released in Jira 8.0.2, just making sure you know about it.
We're updating project and users avatars with new colors and shapes. For details, see EAP 1.
Lazy-load to improve performance
Status: IMPLEMENTED (for details, see EAP 1)
We've introduced lazy loading of card colors and boards in the board picker to improve the overall loading time.
Issue archiving
Status: PARTLY IMPLEMENTED (for details, see EAP 1)
To help keep Jira clean and clutter-free, we've introduced the option to archive individual issues.
Component archiving
Status: PARTLY IMPLEMENTED (for details, see EAP 1)
You can now archive components so that they can't be selected and linked to issues and are marked as 'Archived'.
Implemented changes
In this section we'll provide details of changes we have implemented, organized by the EAP they are first available in.
Changes in this milestone
Lazy loading of card colors and boards in board picker
To make your issues more visible and recognizable on boards and backlogs, you can assign card colors to issue types. However now, we've changed the way those colors are loaded. Introducing lazy loading does not change how the feature works but results in faster boards and backlogs.
Board picker helps you quickly navigate through boards. To optimize response time, we've decided to change the way we load boards for the board picker. Now we load the boards only when you interact with the picker icon, which saves Jira a lot of hassle. In this way, even though we leave the functionality intact, we offer you a faster loading solution.
'Issue details' panel is resizable on Scrum/Kanban boards
Until now, users could manually resize the 'Issue details' panel only on Scrum/Kanban backlogs (you can check how it works there). After receiving many requests, we've also added this possibility to Scrum/Kanban boards. Additionally, we've added a horizontal scrollbar for boards that have many columns and are displayed on small screens.
Column headers limited to 1 line
Column headers will be limited to one line, containing the column name (shortened with ellipsis), and column constraints (min. and max. issues, if enabled).
See before and after...
New avatars
We're updating project and user avatars.
User avatars:
updating colors to match our Design guidelines.
Project avatars:
switching from round avatars to rounded square avatars
updating colors to match our Design guidelines.
See before and after...
Issue archiving for early adopters
Issues can either be archived one by one or in bulk. Once an issue is archived it is removed from the index and disappears from the search results, dashboard, boards, and backlogs.
If needed, individual issues can be restored with a direct link.
The feature is available both using the UI or the REST API.
Currently, the scope of archiving and restoring issues is limited due to the feature being in an early stage of development.
Component archiving
You can now archive components so that they do not clutter your Jira instance. Archived components still show on the components list but are marked as 'Archived' and they cannot be selected in the Component/s dropdown.
The feature is not yet available in Jira Service Desk.
Source
EAP - Jira 8.0.0-RC Release Notes
No significant changes in this milestone
Source
