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

Jira Service Desk リリース ノート

このページの内容

お困りですか?

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

コミュニティに質問

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

As Jira Service Desk runs on the Jira platform, you should also view the Jira platform 8.2 upgrade notes.


 変更の概要


アップグレードノート

Here's a summary of changes and important notes from Jira Service Desk 4.2.


The issue JRASERVER-69388 related to all Jira 8.2.x versions released so far has been fixed in Jira 8.2.4. Upgrading to Jira 8.2.4 will prevent the issue from affecting new data. However, the upgrade won’t fix the already existing problems. We are working on a solution for this as well.

If you're on version 8.1.x (or older) we recommend that you to upgrade to Jira 8.2.4.

Java 11 のサポート

Java 11 is now officially supported! For more details, see Supported platforms.

If you're using SQL Server as the database, note that we've updated the Microsoft JDBC driver bundled with Jira to version 7.2.1. This version is required to use Java 11.


Running Jira with Microsoft SQL Server 2017

You can now run Jira with Microsoft SQL Server 2017. For more info, see Connecting Jira to Microsoft SQL Server 2017.


サポート終了のお知らせ

In Jira Service Desk 4.2, we're making the following changes:

  • Removing 32-bit installers. The 32-bit installers are no longer available to download. If you need to stick to 32-bit systems, you can still install Jira by using the zip/tar.gz archives, as described here.
  • Advance notice: End of support for several built-in importers. In Jira 8.4, we will drop support for built-in importers that are dedicated to specific applications, like Asana, Bugzilla, Pivotal Tracker, etc. You will still be able to import data to Jira, provided that you use the CSV or JSON format.

For more info, see End of support announcements.


アプリ開発者向けの情報

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

Customer portal changes

ヘルプ センターとカスタマー ポータルのルック アンド フィールにいくつかの変更を行いました。これは、カスタマー エクスペリエンスをシンプルかつ洗練されたものにするための改善の第 1 段階です。

これを行うため、フロントエンドのコードベースにいくつかの変更を加える必要がありました。これによってサードパーティ アプリが影響を受ける可能性があります。

潜在的な影響

次の 2 つの点に注意してください。

  • レイアウトの変更は、カスタマー ポータルでのアプリの表示方法に影響を与える可能性があります。
  • カスタマー ポータルは非同期的にルートを読み込むため、これまでは利用可能だったグローバルに影響を与える可能性があります。


Click here to see full list of dependencies impacted...

Web-resource dependencies with side-effects that are impacted:

com.atlassian.auiplugin:aui-spinner
jira.webresources:jquery-spin
com.atlassian.auiplugin:aui-header
com.atlassian.auiplugin:soy
com.atlassian.auiplugin:aui-button
com.atlassian.plugins.atlassian-chaperone:hotspot-tour
com.atlassian.plugins.atlassian-chaperone:chaperone
jira.webresources:jquery-ui-draggable
com.atlassian.auiplugin:jquery-ui-focusable
jira.webresources:jquery-progressbar
com.atlassian.auiplugin:table
com.atlassian.plugins.atlassian-plugins-webresource-plugin:data
com.atlassian.soy.soy-template-plugin:soy-deps
com.atlassian.auiplugin:aui-lozenge
com.atlassian.auiplugin:aui-toggle
com.atlassian.auiplugin:aui-badge
com.atlassian.auiplugin:ajs
jira.webresources:calendar-lib


Web-resource dependencies that expose AMD-modules that are impacted:

jira.webresources:calendar (contains the following AMD-Modules): jira/libs/calendar, jira/libs/calendar-layerable-mixin
jira.webresources:jquery (contains the following AMD-Modules): jquery, jira/jquery/deferred
jira.webresources:jira-logger (contains the following AMD-Modules): jira/util/logger
jira.webresources:jira-formatter (contains the following AMD-Modules): jira/util/formatter
jira.webresources:wrm-context-path (contains the following AMD-Modules): wrm/context-path
jira.webresources:feature-flags (contains the following AMD-Modules): jira/featureflags/feature-manager
jira.webresources:jira-metadata (contains the following AMD-Modules): jira/util/data/meta, jira/util/data/meta/store, jira/util/strings
com.atlassian.auiplugin:dialog2 (contains the following AMD-Modules): aui/dialog2
com.atlassian.auiplugin:aui-flag (contains the following AMD-Modules): aui/flag
jira.webresources:aui-core-amd-shim (contains the following AMD-Modules): aui/dialog, aui/dropdown, aui/message, aui/params, aui/progressive-data-set, aui/popup, aui/tabs, aui/inline-dialog
jira.webresources:jira-analytics-amd (contains the following AMD-Modules): jira/analytics
jira.webresources:util (contains the following AMD-Modules): jira/legacy/meta, jira/ajs/ajax/ajax-util, jira/util/version, jira/data/parse-options-from-fieldset, jira/ajs/persistence, jira/xsrf, jira/ajs/default-custom-event
jira.webresources:jira-urlhelpers (contains the following AMD-Modules): jira/util/urls
com.atlassian.plugin.jslibs:marionette-1.4.1-factory (contains the following AMD-Modules): atlassian/libs/factories/marionette-1.4.1
com.atlassian.plugin.jslibs:brace-2014.09.03-factory (contains the following AMD-Modules): atlassian/libs/factories/brace-2014.09.03
com.atlassian.plugin.jslibs:skate-0.12.6 (contains the following AMD-Modules): atlassian/libs/skate-0.12.6
com.atlassian.plugin.jslibs:backbone-1.0.0-factory (contains the following AMD-Modules): atlassian/libs/factories/backbone-1.0.0
com.atlassian.plugin.jslibs:underscore-1.4.4 (contains the following AMD-Modules): atlassian/libs/underscore-1.4.4
com.atlassian.auiplugin:aui-form-validation (contains the following AMD-Modules): aui/form-validation, aui/form-validation/validator-register
com.atlassian.auiplugin:aui-inline-dialog2 (contains the following AMD-Modules): aui/inline-dialog2

If you use globals, for example AJS.dialog2, instead of require ('aui/dialog2'), it's a good time to make these changes.

実行内容

4.2 では特別な操作を行わない場合、アプリがこれらの変更の影響を受ける可能性があります。

手順

  1. Check that the dependencies your app needs are specified in your web resources. When checking this, consider if these dependencies are necessary, or if they're negatively impacting load-time performance. You can use https://bitbucket.org/atlassianlabs/atlassian-webresource-webpack-plugin to help achieve this.
  2. 新しいレイアウトでアプリの動作が期待通りであることを確認します。サービス デスク管理者が新しいレイアウトをアクティブ化すると、<body> 要素にクラス custom-portal-layout-flag が含まれるようになります。

We'll be releasing an Early Access Program to give you time to test your changes before general release.

If you have a question

You can post any questions to this community page and we'll get back to you as soon as we can.


アップグレード手順

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.2.


最終更新日 2019 年 7 月 22 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.