Jira Service Desk 3.14.x アップグレード ノート

Jira Service Desk リリース ノート



アトラシアン コミュニティをご利用ください。


Here are some important notes on upgrading to Jira Service Desk 3.14. For details of the new features and improvements in this release, see the Jira Service Desk 3.14 release notes. As Jira Service Desk runs on the Jira platform, you should also view the Jira platform 7.11 upgrade notes.

アップグレード ノート

Jira Service Desk 3.x is a major upgrade

If you're upgrading from Jira Service Desk 2.x, be sure to read these upgrade notes thoroughly, take a full backup, and test your upgrade in a non-production environment before upgrading your production site.

Jira 管理者

Apache Tomcat のアップグレード

In this release, we've upgraded Tomcat to version 8.5.29. 

IPv6 のサポート

We now support running Jira in an IPv6 environment. We’ve taken the dual-stack approach (IPv4 + IPv6), so your IPv4 addresses will still work. In most cases there’s nothing you need to do, however there are a few things that you need to be aware of.

  • Must allow IPv4 traffic
    Some parts of Jira, listed below, require IPv4. Enabling the IPv4 traffic is not mandatory, but you won't be able to use these features without it:
    • Atlassian Marketplace
    • Atlassian Cloud 製品との連携
    • ログ アナライザー
    • サポート終了の確認
  • Avoid using raw IPv6 addresses anywhere in the Jira configuration
    We recommend that you use hostnames or domain names instead of IPv6 addresses. It's a more reliable way of configuring and accessing both Jira and other Atlassian products.
  • Avoid using raw IPv6 addresses in the browser
    Rich Text Editor won't work if you access Jira through a plain IPv6 address in the browser. It will work when you use a hostname.
  • AWS Relational Database Service (RDS) doesn't support IPv6
    For this reason, our CloudFormation template and Quick Start (deploying Jira Data Center into AWS) will continue to provision an IPv4 Amazon VPC.
  • Problems with cache replication for Jira Data Center on Linux
    The cache replication tries to use the IPv4 address instead of IPv6 as an RMI endpoint, and fails if IPv4 is disabled on your system.


    If your systems are IPv6 only, you can work around this issue by setting the java.rmi.server.hostname  system property to your IPv6 address. For example:



See Preparing for Jira 7.11 for any important changes regarding plugins.



すでに Jira のいずれかのバージョンをご利用中の場合は、以下の説明に従って最新バージョンにアップグレードします。

  1. アップグレードする前に、インストール先のディレクトリ、ホームディレクトリ、およびデータベースをバックアップされることを強くお勧めします。
  2. リリース ノートとアップグレード ガイド (ご利用のバージョンから最新バージョンまでのすべてのリリース分) を読みます。
  3. Download the latest version of Jira Service Desk.
  4. アップグレード ガイド」の説明に従います。


Check the Jira application compatibility matrix to ensure you have the most up to date, compatible versions.

  • 3.1, or later
    There are no known issues.
  • 3.0
    There is a known issue regarding gadgets, and there is a workaround described in the JIRA Service Desk 3.1.x upgrade notes.
  • Earlier than 3.0
    Please consult the Migration hub as it contains information on important user management, application access and log in changes. You  must upgrade to JIRA Service Desk 3.0 before upgrading to Jira Service Desk 3.14.
最終更新日 2019 年 6 月 20 日


Powered by Confluence and Scroll Viewport.