Preparing for Jira 7.12

This page covers changes in Jira 7.12 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. 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.12 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 Jira REST API.

We will update this page as development progresses, so please stay tuned for more updates. We also recommend following the Jira news on Atlassian Developer 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" section and you don't make the necessary changes.

Changes

Jira Service Desk is deprecating com.atlassian.fugue in 3.15

Jira Service Desk 3.15 is deprecating the use of com.atlassian.fugue. In Jira Service Desk 4.0, we'll be permanently removing com.atlassian.fugue and updating our APIs to use Core Java Data types and Exceptions instead. Read the full deprecation notice for more information and post any questions in the Atlassian Developer Community.

PostgreSQL 9.3 deprecated in Jira 7.12

Jira 7.12 has deprecated the use of PostgreSQL 9.3. In Jira 8.0, we'll be permanently removing the support for PostgreSQL 9.3. For more info, see End of support announcements.

<user-data> removed from JSON

For security reasons, we have removed the <user-data> attribute from the JSON that displays when you view page source for an issue.

Days in column optional for boards

You can now decide if you want to have the Days in column time indicator disabled for all your Scrum and Kanban boards. Disabling Days in column can significantly improve Jira performance. For more info, see Release notes.

Custom fields optimizer (Jira Data Center)

You can now find custom fields whose configuration is not optimal, and improve them with a click of a button. For more info, see Release notes.

Atlassian User Interface (AUI) upgrade

Jira 7.12 will have a new version of Atlassian User Interface (AUI), upgrading from 7.8.0 to 7.9.6. The new version includes changes to multiple drop-down menus. For more info, see AUI upgrade guide.

Share edit rights for filters and dashboards

We’ve added new permissions to filters and dashboards, allowing you to choose who can edit or view them. What’s more, you can now share filters and dashboards not only with projects, groups, and roles, like it was before, but also with single users. You can see some examples and screenshots in the Release notes. Below you can also find some changes to REST APIs.

REST API changes

When improving the filters, we’ve modified some of the existing APIs, mostly adding new fields. We haven't made any changes to the APIs related to dashboards. Expand the sections below for more info.

**Retrieving/changing filter's details**

Method	Changes
GET filter/{id} PUT filter {id} POST filter {id}	Added a new field to the FilterBean class: editable (boolean). It tells you whether the user retrieving information about the filter has permission to edit it.

**Adding permissions to filters**

Method	Changes
POST filter/{id}/permission	- new option for the type parameter: user (allowing you to grant permissions to a single user) - new parameter: userKey (describing the user for whom you're changing the permissions) - new parameters: view (boolean) and edit (boolean) (permissions you're granting)

Note: To give edit permission, you need to specify both view and edit as true. If you specify only one parameter, or none at all, view permission will be granted by default.

**Retrieving filter's permissions**

Method	Changes
GET filter/{id}/permission	The following 3 new fields are returned: - user - view (boolean) - edit (boolean)

Download EAP