Jira 8.14 への準備

This documentation is intended for Jira developers who want to ensure that their existing apps are compatible with Jira 8.14. 

概要

最新バージョン

ここでは最新の EAP についての情報をご案内します。

アプリケーション / 日付

EAP 番号

バージョン (Maven)

ダウンロード

Jira Core/Software

 

8.14.0-rc01

8.14.0-m0005

EAP

Source files (Core)

Source files (Software)

Jira Service Desk

 

4.14.0-rc01

4.14.0-m0005

EAP

ソース ファイル

変更の概要

In this section we'll provide an overview of the changes we intend to make in Jira 8.14, so you can start thinking how it might impact your apps. Once they're ready, we'll indicate when a change has been implemented, and in which milestone. 

Improvements to email templates (Data Center)

Status: IMPLEMENTED (eap 01)

We’ve made the following improvements to email templates in Jira:

  • Download/upload: Added a new Email templates page in Jira where you can download a ZIP archive with all available templates and upload it back once you’re done editing. This should give you easy access to your templates, without the need to retrieve them from various plugins or directories.
  • File validation: We’ll check the structure of the ZIP archive you uploaded to make sure all the important files are where they should be.
  • Retained on upgrade: Moved the email templates to the Jira shared home directory. Thanks to that, you won’t have to copy over your customizations with every upgrade.
  • No restart needed: You can upload and apply the new changes without restarting Jira.
  • Revert to default: Added an easy way to revert to default templates, just in case something isn’t right.

For more details, see Email templates.

Issues in epic displayed in the detail view

Status: IMPLEMENTED (eap 01)

When you open an epic, issues that belong to it are displayed in the Issues in epic section. We’ve added this section also to the issue detail view, letting you quickly see what needs to be done. The detail view for epics is only displayed on Kanban boards where you can choose to show epics as cards.

Set context for custom field when you create it

Status: IMPLEMENTED (eap 01)

To help you limit the number of global custom fields that affect Jira's performance, we've added an option to set the custom field's context while creating it. Now, instead of going to the CF configuration and updating the context, you can set it as part of the creation flow (either in the Administration area or in the Issue view).

Passing credentials via URL parameters no longer possible

Status: IMPLEMENTED (eap 01)

In Jira 8.14 and later we’ll be blocking the default possibility to log into Jira by passing credentials via URL parameters (see https://jira.atlassian.com/browse/JRASERVER-38548).

This method of authentication has been deprecated since the release of Jira 8.0 on 11th Feb 2019 (see https://jira.atlassian.com/browse/JRASERVER-67979).

ロード バランサやプロキシなどの別のログ ファイルでは資格情報がプレーン テキスト エントリとして表示される可能性があるため、このメソッドにはセキュリティ リスクがあります。これを最小化するため、このデフォルト機能を廃止し、特別な場合にのみ使用するオプションにすることを考えています。また、Jira に組み込みの Tomcat web サーバーのアクセス ログの見直しも行います。

しかしながら、内部連携や従来の連携が引き続き動作できるようにするため、このメソッドを使用できる方法は今後も提供します。特別なシステム プロパティ atlassian.allow.insecure.url.parameter.logintrue に設定する必要があります。これにより、従来の連携や内部連携は引き続き動作します。ログを制御下におくため、ログを見直して資格情報のエントリがあるかどうかを確認することもおすすめします。

パーソナル アクセス トークン

Status: IMPLEMENTED (eap 01)

Jira の REST API は、自動化や他のシステムとの連携の無限の可能性を実現します。安全性を考慮し、パーソナル アクセス トークンを作成できるようになりました。これは、認証にユーザー名とパスワードを使用している場合の安全な代替策になります。

トークンの作成と取り消し 

Head to your profile, and choose Profile > Personal Access Tokens to create a token. You can create as many different tokens as you need, and set different expiry dates for each. 
If a user's account is disabled or deleted, their token will no longer work. 

トークンの管理 

Administrators can use system properties to limit the number of tokens people can create, and set expiry rules.
If you have Jira Data Center, system administrators can also see all tokens, and revoke them at any time.  

For an overview of all personal access token available in you instance, head to Administration > System > Administering personal access tokens 

jQuery のアップデート

Status: ADVANCE NOTICE 

In Jira 8.15 (due around January/February) we plan to apply some security patches to jQuery 2.2.4, which is bundled with Jira. This introduces a breaking change which affects any single tag HTML strings parsed via jQuery.

ここをクリックして展開...

次のような例があります。

jQuery('<div/><span/>');

パッチ適用前の上述のコードは、次のように変換されます。

<div></div>
<span></span>

しかし、パッチ適用後は、明示的に閉じられていない単一のタグはネストされます。

<div>
	<span></span>
</div>

つまり、単一タグの HTML は、次のように明示的に開始タグと終了タグを持つように変換する必要があります。

jQuery('<div></div><span></span>');

The above change affects the jQuery()jQuery.htmlPrefilter, and all jQuery DOM manipulation methods (append, after, appendTo, before, html, insertAfter, insertBefore, prepend, prependTo, replaceWith, wrap, wrapAll, wrapInner).

This change will affect any plugins which utilise the jQuery bundled with Jira.

影響を受けないケース

次のようなケースは、変更による影響を受けません。 

  • 次のような単一タグの HTML 自体:

    jQuery('<div/>');

    ネストするための追加の HTML タグがないため、単に次のように変換されます。

    <div></div>
  • Void elements don't require explicit opening and closing tags. For example:

    jQuery('<br/><div></div>')

    次のように正しく変換されます。

    <br>
    <div></div>

詳細情報

Although we're not upgrading our jQuery library to version 3.5, we are cherry-picking and applying some patches from that version. See https://jquery.com/upgrade-guide/3.5/ for a good explanation on the breaking change.

埋め込みの Crowd のアップグレード

ステータス: 実装済み

We’ve upgraded Embedded Crowd, which gives you access to some of the Crowd 4.2 features inside of Jira. An important one is the ability to encrypt database passwords to external user directories. With this improvement backed up passwords will be also encrypted.

New version of DVCS Connector bundled with Jira

Status: IMPLEMENTED (eap 01)

After releasing two EAPs of the new DVCS Connector, we'll be bundling it with Jira. Here's some highlights of the improvements:

Supportability

  • Improved logging being exposed by the plugin to aid in root cause analysis of production issues.
  • Introduce the Atlassian profiling framework to allow customers and support teams to profile sync operations.

ユーザー インターフェース

  • Add pagination to repository lists and organizations/accounts, and limit it to 100 elements.
  • Collapse organizations on page load and lazily load when expanded.
  • Improve loading mechanisms to improve performance.

Sync

  • Move away from performing full syncs to pull in all historical data by default, but instead leave it as an option for users.
  • Move from polling to event-driven architecture.

GitLab

  • Add support for GitLab

To read more about these changes, and test the latest EAP, see DVCS Connector EAP.

Jira Service Desk is now Jira Service Management JIRA SERVICE MANAGEMENT

Status: IMPLEMENTED (eap 01)

Starting from version 4.14, Jira Service Desk becomes Jira Service Management. You might have already seen this new name on some of our pages, as we coordinated updates with our Cloud counterparts, but the official version that brings this change is 4.14. Here’s a summary of what changes:

What changes right now

  • Any text occurrences of Jira Service Desk in-product (apart from things mentioned in the next section)
  • ロゴ
  • Project type: "Service Desk" > "Service"
  • Project template: "IT Service Desk" > "IT service management"
  • URLs to docs or Atlassian pages. They will keep working with redirects, so don't worry if you're using them in your app.

このバージョンでは変更されない要素

  • All roles and permissions: To make things easier, we decided to keep current roles and permissions intact. This includes roles like Jira Service Desk Customer - Portal Access or Service Desk Team. We might change them in future releases, but we’ll let you know before that happens.

  • Occurrences of servicedesk in the code: We’re not changing occurrences of servicedesk in the code, so don’t worry about this change affecting your app too much. This applies to things like servicedesk-id or service_desk as type of project.

  • Public or private APIs: We’re not changing any APIs right now, so your development process should remain the same.

Recommendations for changing text references to JSD in your app

Expand for details...

Here are some recommendations that we’ve been following, in case you needed to call things differently in your app.

Term substitution

Original

Change to

Jira Service Desk

Jira Service Management

Service Desk project / service desk project

service project

service desk

service project

service desk software

service management software

Service Desk agents / customers

You’ll need to decide this one based on context.

  • If it’s the name of a role, don’t change it.

  • If it refers to agents of your instance in general, you can say Jira Service Management agents.

  • In some cases, where it was clear we’re referring to agents from a specific project, we said “service project agents”.

Capitalization

The most common changes included changing “Service Desk project” or “service desk” to service project. Note that “service project” should always be sentence-case, that is project should never be written with a capital P. For example:

  • You don’t have permission to access this service project.

  • Service projects are available in a variety of templates.

What to watch out for

You’ll probably be using a lot of find+replace (wink).

  • One thing we’ve noticed is that many people tried to replace “Service Desk” with “service project” which ended up with many “service project project” (the original was “Service Desk project”). Just keep that it mind.

  • Likewise, we call these projects “service projects” and not “Jira Service Management projects”, although this one is not that bad. Still, try using service projects, unless you really want to emphasize they come from Jira Service Management. We aim to have business, software, and service projects.

お困りですか?

If you’re not sure how to rebrand something or need extra help, feel free to comment below this post on dev community. We’ll try to help.

New audit log events in advanced auditing (Data Center) JIRA SERVICE MANAGEMENT

Here's a list of new events that we're adding to the advanced audit log:

  • SLA 条件の作成
  • SLA 条件の更新
  • プロジェクトに組織を関連付け
  • プロジェクトから組織の関連付けを解除
  • JSM 通知ルールのテンプレートの更新
  • メール チャネルの更新 (パスワードの変更)

最終更新日 2020 年 11 月 19 日

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

はい
いいえ
この記事についてのフィードバックを送信する

このセクションの項目

Powered by Confluence and Scroll Viewport.