Meelogic Atlassian Blog

Jira Software 8.6 release notes

✓ Jira copies over changes files on upgrade

✓ New JVM code cache check

✓ Replying to JIRA notifications in Outlook made way better

✓ Users and roles made better

✓ PostgreSQL 10 comes to Jira

✓ Several older platforms get deprecated

✓ Prefix and suffix search

✓ Accessible dropdown menus

✓ Configurable scheme parameters in Jira REST API for projects creation

✓ Burnup charts in Jira Software

✓ Self-protect and sleep easy with rate limiting

✓ New information in the audit log

✓ Cluster monitoring

Jira copies over changes files on upgrade

Now you no longer need to copy the changed files to keep your customizations after the upgrade. Jira will recognize the files you changed in your old version and copy them to your new Jira instance. In the meantime, you can just sit back and try out new features.

New JVM code cache check

This new check verifies that you’re using the recommended JVM configuration for code cache memory. Insufficient code cache memory can impact performance. This check is already available to customers who manually update the ATST app to 1.30.0. It will run automatically.

Replying to  Jira notifications in Outlook is now way easier

In response to many requests, Atlassian has found a solution for customers that will allow their users to respond to Jira notifications and leave comments in tickets using Outlook. As part of the changes it was decided to discard two email handlers (“Add a comment from the unquoted email body” and “Create a new task or add a comment to an existing task”).

Users and roles made better

Atlassian has improved the Users and Roles page within the project settings. This allows project administrators to quickly add people to a project and assign them all the roles they need.

Now it is more about assigning roles to a user than adding users in roles. You can also search for users, view and select roles in a drop-down menu, or view all users and their roles in a single list with nice columns. You can check this under Project Settings > Users and Roles.

PostgreSQL 10 comes to Jira

A new database has been added to the supported platforms: PostgreSQL 10.

…and some older platforms get deprecated

Adding new databases means that not all of the old databases can be supported:

SQL Server 2012

PostgreSQL 9.4


Orakel 12c R1

PostgreSQL 9.5

MySQL 5.6

SQL-Server 2014

These are no longer supported in Jira 8.8, with the exception of MySQL 5.6 and SQL Server 2014, which will be available until Jira 8.10.

Prefix and suffix search

Are you stuck when you search for a topic because you can’t remember the exact name? Since Jira 8.0 there is the prefix search:

text ~ "work*"

Now a suffix search has also been added so that you can find exactly what you need in no time:

text ~ "*box"

Accessible dropdown menus

To improve the usability of the “More” menu in the view of an operation and the context menu that is displayed after a right click in the backlog, a scrolling functionality has been added that allows you to see all elements of the list.

Configurable scheme parameters in Jira REST API for projects creation

Now you can fully automate the creation of new projects with specific workflowSchemes. The Jira REST API has been extended accordingly and new endpoints and parameters have been added:

  •  POST /rest/api/2/project with a new optional workflowSchemeId field to create a project and assign a worflowScheme
  • GET /rest/api/2/project/{projectKeyOrId}/workflowscheme to get info about workflowScheme configured for a project

Burnup charts in Jira Software Server

Keep teams on track with a visual representation of a sprint’s scope and identify problems such as scope creep or a deviation from the planned project path. So far available in Jira Cloud offering, now burnup charts are also available in Server.

You can find your team’s burnup chart in the Reports section together with other reports.

More granular sprint permissions

To the existing Manage Sprints privilege set, which allows you to perform all sprint related tasks, the Start/Perform Overall Sprints privilege set has now been added, which allows a user to start and stop a sprint when the dates or duration are set, and the Edit Sprints privilege set, which allows a user to edit the name and destination of the sprint. This allows you to configure your permissions in more detail and granularity and assign tasks to specific users.

Self-protect and sleep easy with rate limiting DATA CENTER

Without protection, automated integrations and scripts can overwhelm your Jira instance with huge requests, resulting in performance degradation and downtime. This causes unnecessary work for admins, who are beeped (often after hours) to fix problems and then have to scour the logs to find the culprit so it doesn’t happen again.

Rate limiting changes all this by giving your Jira instance the power to self-protect. Admins can now control how many REST API requests automations and scripts can make, and how often they can make them, meaning increased performance and team productivity (and hopefully for admins, more sleep too).

New information in the audit log DATA CENTER

As admin you now have more insight into what is going on on your instance. Other important events have been added to the log to give you a more complete set of information to track and manage.

This is the new information available:

  • Dark feature enabled/disabled
  • Jira service deleted
  • Project role created
  • JMX monitoring enabled/disabled

Cluster monitoring  DATA CENTER

The capabilities of the Atlassian Cluster Monitoring plugin have been enhanced. This was previously bundled with Confluence and Crowd to also monitor Jira clusters.

This gives you more tools to manage your data center nodes. All your clustered nodes are displayed on a separate page with information on node availability (since last reboot), ID, load and storage. However, the list only shows the active nodes, so if a node is not available, it will not be displayed. The information available on the page can also help you decide whether a node you have just added to the cluster is configured correctly.

The page is available to Jira system administrators.

To view the clustering information, go to Jira Administration > System > Clustering. To expand and view the runtime and system information, click More for a specific node.