Jira Service Desk 4.13.x upgrade notes

Jira Service Management Release Notes

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Below are some important notes on upgrading to Jira Service Desk 4.13. For details on the new features and improvements in this release, see the Jira Service Desk 4.13.x release notes.

 Summary of changes


Upgrade notes

We normally do not introduce new features in the Long Term Support release but rather consolidate the ones we've introduced since the last Enterprise releases. See our change log for all the features and fixes between the last LTS releases. Learn more

Known issue: Modal dialogs don't open on pages that use cross-origin iFrames

A number of actions in Jira are configured in modal dialogs (pop-ups) — for example, when you click Edit next to an item, we’ll often open the edit settings in the modal rather than move you to a separate page.

Problem

In Jira Service Desk 4.12.2 and 4.13.0, these modal dialogs might not open on pages that use cross-origin iFrames. An example of this could be a cross-origin iFrame added to the Jira banner to collect some statistics. Because of this problem, you won’t be able to complete actions that rely on modal dialogs — these might include editing permissions, starting sprints, or editing comments in Jira Service Management requests. More about this bug

Affected versions

  • 4.12.2, 4.13.0

Fixed versions

We have already fixed this problem in the following bugfix releases:

  • 4.12.3, 4.13.1

Known issue: Jira doesn’t recognize a MySQL database after the upgrade

If you're using a MySQL database, you might get the following error after the upgrade:

We can't tell what database you're using

That’s because your dbcongig.xml file is using mysql as the database-type. This type is no longer recognized by Jira after we ended support for MySQL 5.6, so you’ll need to update it.

To solve this issue:

  1. Stop Jira.
  2. Edit the dbconfig.xml file (in your home directory)
    • If you’re using MySQL 8.0, change the database-type to mysql8.
    • If you’re using MySQL 5.7, change the database-type to mysql57.
    • If you're using MySQL 5.6, you will need to upgrade your database first, as this version is no longer supported.

For more info about connecting Jira to MySQL, see:

End of support announcements

In Jira Service Desk 4.13, we're not making any changes. For previous announcements, see End of support announcements.


App developers

See Preparing for Jira 8.13 for any important changes regarding apps.


Upgrade procedure

We've prepared a dedicated upgrade guide for upgrading between Enterprise releases. See Long Term Support release upgrade guide.

Last modified on Dec 4, 2020

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.