Jira Service Desk 4.12.x アップグレード ノート
Here are some important notes on upgrading to Jira Service Desk 4.12. For details on the new features and improvements in this release, see the Jira Service Desk 4.12.x release notes.
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.
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
- 4.12.2, 4.13.0
We have already fixed this problem in the following bugfix releases:
- 4.12.3, 4.13.1
Limitation for OAuth 2.0 email channels
If you're planning to reconfigure your projects' email channels to use OAuth 2.0, you won't be able to use POP3 for Microsoft Exchange Online. You can either continue using Basic Authentication until the support is provided or set the email channel using IMAP.
For more info about OAuth 2.0 and email channels, see:
Known issue: Azure SQL is reported as an unsupported database
If you’re running Jira with the Microsoft Azure SQL database, you will get warnings saying that you’re using an unsupported database. That’s because Azure SQL is mistakenly reported as SQL Server 2014, and we’ve ended support for this one in this release.
Solution: We’re working on the update of the Atlassian Troubleshooting and Support Tools app. For now, discard the warnings and wait for the available update. Your database is fine.
既知の問題: MySQL 8.0 が設定エラーと報告される
If you use the Jira configuration tool to connect Jira to MySQL 8.0, the health check will display the following warning about a problem with connection settings:
The following database configuration are not set as per our recommended settings: 'validation query, validation-query-timeout
The warning is caused by missing entries in the
dbconfig.xml file that weren’t added by the configuration tool. To fix this, edit the
dbconfig.xml file and add the following entries and restart Jira:
<validation-query>select 1</validation-query> <validation-query-timeout>3</validation-query-timeout>
An important bugfix requires full reindex
We fixed a bug that caused issues removed from sprint not showing in Burndown Chart or Sprint Report. The problem will automatically be fixed for all the newly created and edited issues and they will display in the Sprint Report and Burndown Chart.
If you are not concerned about the past issues, you don’t have to take any action. However, if you want to be sure all the past and current issues get fixed too, you need to perform a full reindex.
A bug in Tomcat causing issues on upgrade
Tomcat started to use double-quotes as of version 8.5.48 as a result of Expansion of JAVA_OPTS in catalina.sh containing '*' stops startup on linux bug. That's why when you upgrade to Jira Service Desk 4.12 and set parameters in
setenv.bat, make sure that you:
- Don't remove the double-quotes in the
- Set all your parameters in one line without any new line in
Audit log system property change
We've made a change to the system property that can be used to restrict the audit log to system administrators only. Set this property to
true if you want to prevent people with Jira Administrator global permission from accessing the audit log.
Mail server password encryption
We're now using Base64 encoding to encode all new and existing mail server passwords. As a result, the
mailpassword field isn't plain text any longer.
Extended API response to look for archived projects
We've added an archived field with the current status to each project in response to
New events in the Advanced audit log DATA CENTER
We are adding new events to track priority (Created, deleted updated) and secure admin login (websudo) for you to have better insight into your application.
In Jira Service Desk 4.12, we're ending support for:
- MySQL 5.6
- Microsoft SQL Server 2014
For other announcements, see End of support announcements.
See Preparing for Jira 8.12 for any important changes regarding apps.
See Upgrading Jira applications for complete upgrade procedures, including all available upgrade methods and pre-upgrade steps that are required for Jira Service Desk 4.12. For a more tailored upgrade, also check our Pre-upgrade planning tool that will recommend a version to upgrade to, run pre-upgrade checks, and provide you with a custom upgrade guide with step-by-step instructions.