JIRA Software 7.6 Long Term Support release change log

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

JIRA Software 7.6 is a Long Term Support release, and this change log aims to give you an overview of what's changed in the preceding versions. 

About Long Term Support releases
We recommend upgrading JIRA regularly, however if your organisation's process means you only upgrade about once a year, upgrading to a Long Term Support release may be a good option, as it provides continued access to critical security, stability, data integrity and performance issues until this version reaches end of life. 

All changes are divided according to versions in which they were released, but it doesn't mean you have to upgrade through each version separately. You can go straight from 7.2 to 7.6.

End of Life policy

Atlassian supports feature versions for two years after the first major iteration of that version was released. Once a version reaches End of Life, you won't be able to receive support for it. Here are the EOL dates for JIRA 7.2 and JIRA 7.6.

7.2August 23, 2018

Learn more

7.6November 14, 2019

Top features

Here's a summary of the great new features awaiting your users.  

  • Project-level administration.
    Delegate some admin responsibilities to project-level admins, allowing them to edit workflows.
  • Rich text editing, or 'what you see is what you get'.
  • Single sign-on for Data Center.
  • Zero downtime upgrades for Data Center.
Release Notes
  • Extended project-level administration.
    Project-level admins get more privileges when editing workflows and can also edit project's screens. You can also disable this feature.
  • Backlog for your Kanban projects.
  • Exporting issues to HTML.
  • In-app notifications to help you stay up-to-date with license renewals, new versions, and critical changes.
  • Garbage collection logs enabled by default to help you and our Support teams troubleshoot your issues.
Release Notes
  • Improved Kanban backlog: versions and epics panels to let you better manage your releases.
  • Sprint goals: add goals to your sprints to let your team know what you want to achieve.
  • Renaming and deleting inactive or closed sprints.
  • JIRA Software Data Center on Microsoft Azure.
  • Events for creating and deleting issue links.
  • Syntax highlighting for additional 25 languages.
  • New Czech, Estonian, Danish, Icelandic, Norwegian, Romanian, Slovak, and Polish language packs.

Release Notes
  • Project-specific priorities.
  • Live monitoring of your JIRA instance with JMX.
  • Subtasks drag 'n' drop.
  • X-Frame-Options to prevent clickjacking.
  • 7.6.11: Support for OpenJDK 8
Release Notes

Critical bug fixes

Every release contains a bunch of bug fixes. Here's all the ones that were deemed  critical  severity and fixed since 7.2. 

7.3All 7.3 bug fixes
7.4All 7.4 bug fixes
7.5All 7.5 bug fixes
7.6All 7.6 bug fixes

Supported platform changes

From time to time we will add or end support for a platform. Here's a summary of the changes since 7.2. 


Added support for:

  • MySQL 5.7
  • PostgreSQL 9.5
  • Apache Tomcat 8.5.6 (replacing 8.0.33)
Supported platforms

Added support for:

  • PostgreSQL 9.6

Ended support for:

  • PostgreSQL 9.2
Supported platforms
7.5No changes.Supported platforms

Added support for:

  • Apache Tomcat 8.5.29 (added in Jira Software 7.6.9)
Supported platforms

Technical upgrade notes

This table is a high-level summary of the upgrade notes, you should read the full upgrade notes before upgrading. 


Important notes:

  • If you're planning to use MySQL 5.7.6 or later, you'll need to grant your database user an extra permission (REFERENCE).
  • If you're running JIRA over SSL, you'll need to update your server.xml with the correct protocol because of the Apache Tomcat upgrade.
  • We've disabled automatic XML backups. Use your native database tools to create a backup.
Upgrade Notes

Important notes:

  • New options added to the startup files to enable garbage collection. Just a heads up, no actions required.
Upgrade Notes

Important notes:

  • New JDBC driver for Microsoft SQL Server requires a new URL. If you didn't modify the original URL, you can fix it with JIRA configuration tool. If you customized the URL, you might need to change it manually.
Upgrade Notes

Important notes:

  • Changes to priority schemes (project-specific priorities feature) will not affect your current configuration.

Known issues:

  • A fix for duplicated job IDs requires extra steps in some instances, just to be sure (checking the database if the index was created; restarting your JIRA instance.)
Upgrade Notes

Upgrade procedure

You can upgrade to JIRA 7.6 Long Term Support release like to any other version. We recommend that you upgrade directly to 7.6, without any intermediary versions. Use one of the following methods:

Upgrading Data Center with ZDU (zero downtime upgrade) isn’t supported, because this feature was added in JIRA 7.3.

Upgrade now

Last modified on Jun 26, 2020

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.