Preparing for JIRA 7.3

This page covers changes in JIRA 7.3 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.3 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.

On this page:

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/Application Risk level. Affects

Change: Removal of the java screenshot applet

Platform/Application: JIRA platform

 

Risk level: high

 Affects: All IE10, IE9 users

 

Change: Removal of JIRA.ExpandableBlock

Platform/Application: JIRA platform

Risk level: low

 Affects: All consumers of the JavaScript global

Change: New workflow editing permission checks  

Platform/Application: JIRA platform

Risk level: low

 Affects: Extensions of Workflow Designer

Change: New version of AUI: 6.0.0

Platform/Application: JIRA platform

Risk level: low

 Affects: Add-on developers

Change: Tomcat 8.5.6

Platform/Application: JIRA platform

Risk level: medium

 Affects: Add-on developers, sys admins

Supported platforms

The definitive list of supported platforms will be released with the official documentation for JIRA 7.3, here we hope to give you advanced warning of platforms we're adding or removing so you may add support to your add-on.

Databases:

Platform Support added or
removed
PostGres 9.5 added
MySQL 5.7 added

Tomcat:

Platform Support added or
removed
8.5.6 added
8.0.33 removed

 

 

JIRA platform changes

Rich Text Editor for JIRA

The WYSIWYG editing experience introduced in JIRA 7.2 as a Labs feature is now enabled by default on all fields configured to use the wiki renderer. You can still opt out as a user or admin.

Interested in writing a plugin for Rich Text Editor? Check these tutorials:

Removal of the java screenshot applet

HTML5 copy-paste of images is supported in all browsers except IE10 and IE9. As we no longer support these browsers, we have removed the java applet from our codebase.

Removal of JIRA.ExpandableBlock

This JavaScript global was a legacy component, deprecated in 2010.

The jira/toggleblock/toggle-block AMD module provides equivalent functionality to what the ExpandableBlock global provided.

New version of AUI: 6.0.0

Minor bugfix, performance improvements, removed Raphael and eve.js libraries.

View in JIRA...

What actually changed from AUI 5.10.1: https://bitbucket.org/atlassian/aui-adg/branches/compare/6.0.0..5.10.1

New workflow editing permission checks

com.atlassian.jira.bc.workflow.WorkflowService has the new method: hasEditWorkflowPermission(ApplicationUser, JiraWorkflow) which should be used to check whether the given user can edit a workflow. Old checks based on global administrative permissions are no longer sufficient.

Tomcat 8.5.6

We've upgraded the bundled version of Tomcat in JIRA to Tomcat 8.5.6. You can check the release notes for Tomcat for more information.
Possible problems which may be encountered: 

  • RFC6265 is now a default cookie specification, so all cookies must be compliant with it.
  • According to RFC 7230 tomcat stopped returning reason phrases in HTTP/1.1 response messages. So the client code may fail if it checks text of message instead of code.

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.

Was this page helpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport