JIRA 7.2.x platform release notes

23 August 2016

Atlassian is proud to announce the release of the JIRA 7.2 platform. If you're upgrading, remember to review the upgrade notes.

The 7.2.x changes described on this page apply to JIRA Core 7.2.x, JIRA Software 7.2.x, and JIRA Service Desk 3.2.x, unless stated otherwise.

For more detailed information on what the changes mean to you if you're upgrading from a version of JIRA earlier than 7.0 to the JIRA 7.2.0 platform, we strongly recommend you read our migration hub documentation, which will walk you through the upgrade path, and the changes you can expect when you upgrade, and the upgrade notes for any versions your skipping.

On this page:


These release notes apply to server releases of the JIRA platform. If you are using one of the JIRA Cloud products, read about the latest changes on the Atlassian Cloud release notes blog.

Keeping the project in mind

We started work in JIRA 6.4 on keeping users in the context of the project by introducing the project sidebar. We've iterated on this to include reports and the issue navigator, users can now stay in the context of their project for all their work. We've also extended this to now include you, the administrator. You can now access a revamped project settings page that allows you to administer the project while still in the correct context.



Summary of changes:

  • Project Administration changed to Project settings in the sidebar
  • Project settings opens in the context of your project
  • Details opens in a dialog, and allows you to edit your project's details, including the project category and project key
  • Delete project and Re-index project are now in the Project settings menu

Visual editing and formatting

Users expect to be able to edit and format content, and see what their result would be instantly. Previously, JIRA allowed users to use wiki markdown in it's text fields, but you couldn't see what it would look like unless you previewed it or saved it.... until now. You can now toggle between Text mode, which allows you to view your content with wiki markdown syntax, or Visual mode, which allows you see your content exactly as it'll be saved.

Text mode

Visual mode

In Visual mode, you can format your content by using the toolbar or by using wiki markdown syntax. As soon as you complete your markdown syntax statement, your content will automagically be rendered correctly. If you or your users prefer to work solely in wiki markdown, this feature can be disabled via  > System > Rich text editor.

Components and Versions pages

We've worked on making the Version and Component pages easier to access manage for both JIRA administrators and project administrators. You can now access and manage your projects versions and components directly from your project sidebar, or through links in the project settings if you can't access the project directly. Adding a component or version is also now performed inline, on the same page, so there's no need to flick between pages to see what your additions will look like.


Choose your own adventure!

We've changed the JIRA onboarding experience, both for administrators and users. When an administrator logs on for the first time and selects their language and avatar, they'll land on this screen:



Here they can choose to create a project and jump right into JIRA, create a project with sample data to explore their JIRA application, or import data from an external system. Creating a project with sample data can also be useful for onboarding new users, the projects are created with issues that have real data that explains how to use their JIRA application, things like mentioning other users, commenting, and adding attachments. New users will be presented with a screen that lets them navigate to an existing project, create an issue, or search for issues.



As a JIRA administrator, you can create a project with sample data for each new user, so that they can familiarize themselves with JIRA before they start working on your active projects.

CSV exporter (replaces the Excel HTML exporter)

We've added a CSV exporter to JIRA, which allows you to export your issues in a comma separated value (CSV) format. This has been a much requested feature, as the CSV file format is a flexible format which can be opened with most spreadsheet applications, such as Number, Excel and Google Sheets. Due to the reduced size of CSV files, we've also removed the limit of 1000 issues per export. At the same time as we implemented the CSV exporter, we removed the Excel HTML exporter, as a Microsoft security update stopped these files from opening correctly. For more information, please review this knowledge base article.



When building features and adding functionality, we're very aware that this can cause a degradation in performance, especially in large instances. In JIRA Software 7.2, we've identified key areas of performance for our customers, and worked hard to make sure we either maintained or improved on these areas. We then tested these areas against JIRA 6.4 with JIRA Agile 6.7, to give a comparison. Some highlights of this work include:

  • View issue - We've improved load times and handle throughput better, meaning you can access and interact with the view issue page quicker. Win!
  • Dashboards - server response times are marginally faster, and throughput is significantly faster, meaning your dashboard are available slightly quicker, and are more stable under load. Lots of people can now view your lovely dashboard faster, another win!

Our main focus here was on server responses and throughput, which both affect large instances significantly. We hope you notice these improvements in your JIRA Software instance when you upgrade.


And more...

We also have a number of smaller changes, the little things we do to help make you job that little bit easier:

  • We've changed "Application role" to Application access" in the permission schemes
  • We've added support for Korean, Portuguese and Russian
  • We've upgraded to the current version of the Atlassian User Interface (AUI) to deliver a more consistent UI
  • We've limited the amount of emoticons that can be added to a text field to 1000 (previously this could have caused memory issues)
  • We've added a toggle that allows you to turn off HTML in custom fields (this closes a potential XSS vulnerability, the default for new JIRA 7.2 instances will be OFF, but existing instances will remain ON so that we don't affect existing use of HTML)
  • The JRE version included with the installer has been updated to 1.8.0u102
  • We're adding support for Microsoft Edge browsers, and PostgreSQL 9.4 databases

Changes for developers

If you develop add-ons or write scripts that interact with JIRA, check out the developer changes on our Preparing for JIRA 7.2 page. Here you'll find information on the Atlassian User Interface (AUI) upgrade and more.


Resolved issues

Performance issues

We’ve noticed that versions 7.2.9 and 7.2.10 have performance issues and show errors while opening pages or finishing some actions. This applies only if you’re using postgreSQL and have more than 500k users. To work around it, increase the heap size by 1GB per million users. We’ll release a fix for this in the next bugfix release.

Issues resolved in 7.2.0

Released on 23 August 2016

Key Summary T P Status Resolution


Issues resolved in 7.2.1

Released on 6 September 2016

Key Summary T P Status Resolution


Issues resolved in 7.2.2

Released on 27 September 2016

We'd like to especially call out JRA-23255, which gives admins the option to turn off the ability to publicly share filters. Setting the option to Off won't change any existing filters that are shared publicly, you'll need to manually change them. You can view more details regarding the change on the issue

Key Summary T P Status Resolution


Issues resolved in 7.2.3

Released on 13 October 2016

In this release, we've extended the JIRA installation and upgrade with the option to choose whether you want to start JIRA straight away or delay starting until it suits you. This option was required to allow us to create an Amazon Machine Image (AMI) for JIRA Software Data Center, which is now supported in Amazon Web Services (AWS) as of JIRA Software 7.2.3.

Key Summary T P Status Resolution


Issues resolved in 7.2.4

Released on 2 November 2016

Key Summary T P Status Resolution


Issues resolved in 7.2.5

This release has been canceled due to a bug that affects the JIRA installers, specifically the JIRA Software installers.

More info is available here: JSW-15235 - Getting issue details... STATUS

This bug only affects customers using the installers. If you have upgraded or installed JIRA Software 7.2.5 and require assistance, please contact Support.

Issues resolved in 7.2.6

Released on 7 December 2016

Key Summary T P Status Resolution


Issues resolved in 7.2.7

Released on 29 December 2016

Key Summary T P Status Resolution


Issues resolved in 7.2.8

Released on 14 March 2017

This release contains important fixes to caches and Lexorank that mainly affect our JIRA Software Data Center customers, and an additional function that allows you to suspend Lexorank rebalancing.

Key Summary T P Status Resolution


Issues resolved in 7.2.9

Released on 25 May 2017

Key Summary T P Status Resolution


Issues resolved in 7.2.11

Released on 26 September 2017

Key Summary T P Status Resolution


Issues resolved in 7.2.12

Released on 4 December 2017

Key Summary T P Status Resolution



Last modified on Aug 21, 2017

Was this helpful?

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