Rate this page:
Note: This documentation is intended for our developer audience. If you are looking for end user documentation, go here instead
You may need to update your plugin to work with JIRA 6.0.
We will update this page as the release progresses. Please watch this page or check regularly to keep on top of changes. Please also see our Java API Policy for JIRA for technical information on the JIRA Java APIs and our approach to changing them.
The major change for JIRA 6.0 is the redesign of the JIRA look and feel, according to the new Atlassian Design Guidelines. Details on this change and others are summarised below.
The JIRA look and feel is being redesigned in JIRA 6.0 according to the new Atlassian Design Guidelines (ADG). We are moving away from JIRA-specific markup patterns in favor of those provided by AUI. This move is an essential part of implementing the Atlassian Design Guidelines in JIRA. Adopting AUI's patterns enables developers to quickly build UI in JIRA that complies with the ADG and works across Atlassian's product suite.
Please see the following guides for details:
With inline edit enabled, document content changes frequently and there are several situations where plugins may need to reconfigure elements (e.g. bind event handlers, create elements). With JIRA 6.0, there are several additional arguments.
Additionally, this statement is no longer true: "It is guaranteed that neither context nor any of its descendants have previously been passed to a handler, so it is safe to assume that they have not been configured."
For more information, please see Guide - Inline edit for JIRA plugins.
JIRA has introduced the ability to edit the username of a User in 6.0. Plugin developers will need to make their plugin work in the case of users with changing usernames; for details, see Renamable Users in JIRA 6.0. Plugin developers that have trouble with unit tests throwing can also find information about the ComponentAccessor on that page.
We have implemented new plugin points for the web panels in the User Profile page. You can override the default 'Details', 'Preferences' and 'Assigned Open Issues per Project' web panels as well as add your own custom web panels.
The Atlassian Plugin Checkup lets you test your plugin's compatibility with different versions of our products. It helps you identify API changes between versions of a product. Also see the Plugins 3 Migration Guide for details on breaking changes.
No features have been removed and we haven't broken any REST APIs in JIRA 6.0. We've added a few items to our REST APIs, but those changes have been very minor. JIRA 7.0 will be our next API breaking release.
We have made changes to JIRA's stable (Java) API. For details on this, see the Clirr results. Also see our Java API policy for JIRA for technical information on the JIRA Java APIs and our approach to changing them.
The Java API changes of note are:
JIRA 6.0 will force velocity files to encode the results of methods. To prepare for this, enable HTML encoding on all of your plugin's velocity files. See the following page for instructions:
JIRA 6.0 will see class and its supporting classes move from JIRA core to the Issue Navigator plugin. IssueTableService can be found at and imported by creating a Component Import Plugin Module.
When we introduced the JIRA API in JIRA 5.0 we added new modules, and , but we left a shaded module for legacy reasons. This has now been removed, so you will have to explicitly depend on the module if you need to depend on implementation classes. Be aware that we can and do change implementation classes often, including in bugfix releases.
If your plugin creates a new Module Descriptor and subclasses or , you may have to make changes to your code as we have removed the deprecated no-args constructor from these classes. You should use the constructor that takes a instead.
The rules for keys that are used in your are much stricter in JIRA 6.0. You must now make sure that the keys that you use for your plugin module descriptors are unique. If they are not unique, the plugin will fail to load and you will see an exception in JIRA's application logs, like the following:
java.lang.IllegalArgumentException: duplicate key: <the-duplicate-key-in-error>
CollectionUtil class has been removed
Previously atlassian-plugin-core contained a series of collection helper classes called com.atlassian.plugin.util.collect.CollectionUtil. This has been removed. Instead you should migrate your code to use the (much better) Google Guava collection classes in com.google.common.base.*
If you want your custom field to be sortable you should create a , and implement or
If you really want your calculated Custom Field to implement , you can still declare it yourself (that is, opt-in). The method has been left in place (for now), it is only the declaration in the class definition that has been removed.
In JIRA 6.0, the length of project names and project keys is configurable. When a JIRA administrator changes the maximum length of these fields, it doesn't affect any existing projects. While creating a project via the ProjectService, the lengths of these values are validated.
The currently configured maximum length for project keys and names in an instance can be retrieved using either of these functions:
The following constants are deprecated and will be incorrect if the value is changed in the configuration:
JSON-P will not be supported in JIRA 6 for security reasons: it is possible for an attacker use this to view information in a JIRA instance that they do not have permission to see.
If you have built integrations that rely on JSON-P, you can override this by setting the system property to .
Please note, the SOAP and XML-RPC remote APIs are being deprecated in JIRA 6.0. They will continue to work without change during the JIRA 6.x lifecycle, however we will not fix bugs nor implement new features related to these APIs. When JIRA 7.0 is released, the code will be removed from JIRA and these APIs will become unsupported by Atlassian. See SOAP and XML-RPC API Deprecation Notice for more details.
Rate this page: