JIRA 5.2 Upgrade Notes
Upgrading to JIRA 5.2 from JIRA 5.1.x
In this section:
Please follow the instructions in the general Upgrading JIRA guide, as well as the JIRA 5.2-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.
Application links can now be configured by administrators
In previous versions of JIRA, only system administrators could configure application links (e.g. link JIRA to Confluence). In this release, JIRA administrators also have access to application links configuration. JIRA administrators will be able to add, modify and remove application links and entity links. However, JIRA administrators will be restricted to using OAuth authentication for application links.
Default notification scheme associated with new projects
The Default Notification Scheme (shipped with JIRA) is now associated with all new projects by default. This means that if you have an outgoing (SMTP) mail server set up, email notifications will be sent as soon as there is any activity (e.g. issues created) in the new project. Existing projects are not affected.
Important information for Japanese customers
Incomplete translations for some JIRA functionality
Translations will be incomplete for a small set of JIRA functionality in this release. This mainly affects text for the new JIRA admin helper feature. Functionality that does not have translated text available will revert to English.
Only the German translations will be 100% complete. We are aiming to provide full French and Spanish translations in JIRA 5.2.1.
JQL history has been removed from the new issue navigator
The new issue navigator no longer has a 'History' section when advanced searching. This section showed the JQL of advanced searches that had been run previously.
JQL History was not part of the new Issue Navigator scope of work, as we felt a lot of users would now be saving their filters which lessened the need for this functionality.
JQL "contains" operator (~) now relates multiple words by AND rather than OR
Previously, if you specified multiple words as the parameter for the "contains" operator (~) in JQL, the words would be logically related by an OR. This has been changed in this release, so that multiple words for a "contains" operator are related by an AND.
For example, if you enter
"issue collector" in an advanced search, it is now equivalent to entering
Known issue using Windows installer to upgrade
(JIRA 5.2.5 and earlier only) A known issue exists with the JIRA Windows installer where it will incorrectly use Tomcat 6 instead of Tomcat 7. This means that the JIRA service will not start after the upgrade. Please see this Knowledge Base article for details of the problem and workarounds.
MySQL driver no longer bundled with JIRA
The MySQL driver is no longer bundled with JIRA. In prior versions of JIRA, we shipped the MySQL driver under a commercial license from MySQL Americas, Inc. MySQL Americas, Inc. was acquired by Oracle Corporation as part of Oracle's acquisition of Sun Microsystems. Oracle no longer offers a commercial license for the MySQL driver on a standalone basis as part of a partner program.
Please note the following if you use JIRA with MySQL:
- Upgrade — If you are upgrading JIRA and you are not using the recommended MySQL driver (JDBC Connector/J 5.1), you must back up the driver from your existing JIRA installation before the upgrade. You will need to copy it into the
libfolder of your JIRA installation after it has been upgraded, as described in Connecting JIRA to MySQL. If you try to upgrade JIRA without doing this, JIRA will fail to start up after the upgrade (you will be able to see MySQL driver-related errors in the logs).
If you are using the recommended MySQL driver (JDBC Connector/J 5.1), you do not need to do this. The driver will be automatically copied over during the upgrade process.
New 'lastViewed' JQL field
The new 'lastViewed' field in JQL (see documentation) lets you search for issues based on the date that they were last viewed/edited. This field is only available for Advanced Search, not Simple Search.
Please note, if you have currently configured your issue navigator to show a column named 'lastViewed' (i.e. you have custom field named 'lastViewed' that you are displaying in the issue navigator), you must rename it before upgrading. If not, the conflict in column names will cause problems with the issue navigator.
Supported platforms changes
- Java 7 and Tomcat 7.0.29 are now supported in JIRA 5.2. See Supported Platforms for details.
- Tomcat 5.5 is no longer supported in JIRA 5.2, as previously advised in this announcement.
- PostgreSQL 8.2 is no longer supported in JIRA 5.2, as previously advised in this announcement.
- Please also read this clarification on browser support for JIRA 5.2 and beyond.
Webhooks JQL filtering may not always match
When an issue is updated, two things are triggered — the issue is reindexed (to ensure the indexes are up to date) and a webhook is fired. If you are using a JQL-based webhook, it will need to confirm whether the issue that has just been updated meets the JQL criteria. The problem is that the reindex may occur after the webhook.
For example, if an issue currently meets the JQL criteria, but you update it so that it does not meet the criteria, the webhook may incorrectly fire anyway. This is because the webhook JQL matching may occur before the issue index is updated.
We are working to resolve this issue in a 5.2.x bugfix release and you can track the progress of the issue here.
Filters that are longer than 2000 characters are not supported
Filters that are longer than 2000 characters – criteria plus value – do not work in the JIRA 5.2.x Issue Navigator.
Information for JIRA developers
Please be aware of the following changes in JIRA 5.2, which are covered in more detail on the Preparing for JIRA 5.2 page:
- Changes to handling Message-IDs on notification emails
- Changes to rendering of block macros
- Newlines in issue Summary no longer allowed
- Easy way to re-use an existing Custom Field Searcher
- New ISSUE_COMMENT_DELETED_ID event
Upgrading to JIRA 5.2 from JIRA 5.0.7 or earlier
Was this helpful?
Thanks for your feedback!