JIRA 6.0 Upgrade Notes

Overview

Please follow the instructions in the general Upgrading JIRA guide, as well as the JIRA 6.0-specific instructions in the sections below. The general 'Upgrading JIRA' guide contains important tasks that are essential for getting your upgraded JIRA installation to work correctly and if necessary, migrating existing configurations.

This page also describes known issues as well as changes you should be aware of before deciding whether or not to upgrade to JIRA 6.0.

This page includes:

Known issues

Migrated pre-6.0 worklogs with mixed-case usernames are disassociated from authors

With the transition in JIRA 6 to user keys in lieu of user names, the pre-6.0 issue worklog is not being migrated correctly in the case of users who had LDAP-originating non-lowercase usernames. This results in the worklog entries not being associated with the user.

(info) This will be fixed in an upcoming release.

JRA-33074 - Migrated pre-6.0 worklogs with mixed-case usernames are disassociated from authors Resolved

Get a sorted list of searchable fields is more than 160 times slower in JIRA 6 than in JIRA 5.2

This comes from the fact that translatable field names was introduced in JIRA 6, which means that JIRA has to get a property set for each field where the translated name is stored when it get the field's name. These property sets should be cached, but that is not currently happening.

(info) This will be fixed in an upcoming release.

JRA-33065 - Searchable Fields Slow - Get a sorted list of searchable fields is more than 160 times slower Resolved

Upgrading to JIRA 6.0 from JIRA 5.2.x

Disabling inline edit no longer allowed

We've removed the ability to disable inline edit because the preferred way to edit issues is with inline editing and we want to encourage use of this feature. This option is no longer available in JIRA Admin (under System > General Configuration).

You may need to upgrade your GreenHopper version to work with JIRA 6.0

GreenHopper versions older than 6.2 will not be compatible with JIRA 6.0.

Cloners workarounds need to be disabled

Any customers upgrading to JIRA 6.0 that applied a workaround for the cloners link type – see clone operation creates link in the wrong direction for details – may need to reverse that workaround.

JSON-P no longer supported

JSON-P will not be supported in JIRA 6.0 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 atlassian.allow.jsonp  system property to true.

Creating a new project: Select Project Type dialog known behaviour

Please note, in JIRA 6.0, choosing Blank Project, Bug Tracking, Software Development or Project Management in the new Select Project Type dialog will create the same default JIRA project. We are in the process of developing pre-configured project templates for project types. We are considering custom workflows, sample data, preset issue types, default fields, etc, for these templates. Your use of the dialog will give us with valuable data to help us build the right project types.

Upgrading to JIRA 6.0 from JIRA 5.1.8 or earlier

In addition to the points listed above, please read the Important Version-Specific Upgrade Notes for every version of JIRA you are skipping.

Information for JIRA developers

JIRA 6.0 is a major release for JIRA. As a result, there are a number of changes that may break add-ons. These include changes to JIRA's stable (Java) API, changes to core JIRA CSS styles, changes to JavaScript components that build UI, changes to HTML markup patterns. For details, please see: Preparing for 6.0.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport