Last updated Apr 11, 2024

Preparing for JIRA 7.2

This page covers changes in JIRA 7.2 that can affect add-on compatibility and functionality. This includes changes to the JIRA platform and the JIRA applications (JIRA Core, JIRA Software, JIRA Service Desk).

As a rule, Atlassian makes every effort to inform add-on developers of known API changes as far in advance as possible. Where possible, we attach release targets. Unless otherwise indicated, every change on this page is expected to be released with the first public release of the JIRA Server 7.2 products. We also make release milestones available prior to the release:

  • For JIRA Server, the JIRA development team releases a number of EAP milestones prior to the final release, for customers and developers to keep abreast of upcoming changes. For more information on these releases, see JIRA EAP Releases.
  • For JIRA Cloud, the JIRA team releases updates to the JIRA Cloud products on a weekly basis. Add-ons that integrate with the JIRA Cloud products via Atlassian Connect should use the JIRA REST API, which is subject to the Atlassian REST API Policy.

We will update this page as development progresses, so please stay tuned for more updates. We also recommend following the JIRA news on Atlassian Developers blog for important announcements and helpful articles.

Summary

The risk level indicates the level of certainty we have that things will break if you are in the "Affected" column and you don't make the necessary changes.

Change. Platform/ApplicationRisk level. Affects

Change: Deprecating JUnit3 test framework

Platform/Application: JIRA platform

Risk level: low

 Affects: Functional test API

 

Change: Removing ExtensionAccessor

Platform/Application: JIRA platform

Risk level: low

 Affects: Plugins using ExtensionAccessor

Change: AUI Upgrade 5.7 -> 5.9

Platform/Application: JIRA platform

Risk level: medium

 Affects: The latest version of AUI removes the aui-inline-dialog2 web component and replaces it with aui-inline-dialog Any usage of aui-inline-dialog2 will need to be replaced with the updated aui-inline-dialog. In additon aui-inline-dialog2 is no longer experimental and is now shipped with AUI. For more information on upgrading aui-inline-dialog2 see: https://docs.atlassian.com/aui/latest/docs/inline-dialog-upgrade-guide.html. Because of these changes any plugin updated to work with the version of AUI shipped with JIRA 7.2.0 will not automatically be backwards compatible with older versions of JIRA.

The AUI upgrade also comes with updated versions of webdriver and selenium. These updates may have an impact on your test infrastructure if you have been relying on AUI for your versions of these libraries.

Change: Updated navigation experience

 Platform/Application: JIRA platform

Risk level: low

 Affects: We introduced an updated navigation experience which updates our existing project sidebar and places it onto all project related pages. This also introduces some performances changes to our UI stack to allow for asynchronous loading of elements. This may impact plugins that use the sidebar. Specifically you should ensure that any interactions with the sidebar are via JIRA.API.getSidebar() rather than the non-promise based JIRA.API.Sidebar.

*\ This\ is\ a\ JIRA\ platform\ feature,\ but\ it\ currently\ only\ works\ for\ JIRA\ Software.

JIRA platform changes

Removing ExtensionAccessor

ExtensionAccessor was introduced in JIRA 7.1 to provide the ability to query for current extensions. In case you used  ExtensionAccessor in your plugin, please revert back to PluginAccessor.

JIRA Core changes

No specific JIRA Core application changes.

JIRA Software changes

No specific JIRA Software application changes.

JIRA Service Desk changes

No specific JIRA Service Desk application changes.

Rate this page: