Automatically show Insight referenced Object attribute values on Jira issue and based on selected Object
プラットフォームについて: Data Center のみ - この記事は、Data Center プラットフォームのアトラシアン製品にのみ適用されます。
この KB は Data Center バージョンの製品用に作成されています。Data Center 固有ではない機能の Data Center KB は、製品のサーバー バージョンでも動作する可能性はありますが、テストは行われていません。サーバー*製品のサポートは 2024 年 2 月 15 日に終了しました。サーバー製品を利用している場合は、アトラシアンのサーバー製品のサポート終了のお知らせページにて移行オプションをご確認ください。
*Fisheye および Crucible は除く
目的
Often Insight administrators and users want to show additional information related to the Object selected on a Jira issue, presented by related (referenced Objects). This article shows how to configure Insight to do that, right after the issue has been created. The result will be that related (referenced) Objects will be stored in separate Custom fields.
ソリューション
- Let's suppose we have a Computer object, that has an Attribute "Type", pointing to another Object called "Computer Type" (which can have values "Desktop" or "Laptop"):
- We created an Insight custom field "Affected Computer" that is visible for Jira user (and / or Service Desk customer) to select. An example configuration:
- Now, we created another Insight custom field "Computer Type" that will pull the value of "Type" attribute from issue context (the Object selected in "Affected Computer"). To automatically fill this custom field with the relevant value (so that a Jira user / customer does not need to select this value manually), we need to make us of "Filter Issue Scope" and "Filter Assign Scope IQL" fields and also check "Make Filter Assign Strict". An example configuration:
${Affected Computer} is a placeholder that will address the selected Computer Object in the context of the current issue. - Now, assuming the screens are configured properly to show "Affected Computer" and "Computer Type" custom fields, when we create a new issue and fill "Affected Computer", the related "Computer Type" value will get automatically filled:
注意
- Additional Object attributes' values can be also shown by adding them in scope of "Object attributes on Issue view" field, when configuring the custom field.An example configuration and the result can be seen below.
However, on Service Desk customer portal, it is not possible to extend Object information in such way. Therefore, storing object attribute values and referenced objects into separate custom fields is the way to go. - To store other Insight attribute values (non-Object attribute type) into regular Jira custom fields, you can use Insight workflow post function "Set a Jira custom field with the attribute value from a selected object" to do that.
The Filter Issue / Assign Scope IQL in the "Computer Type" custom field in the above screenshot is written in a form supporting only a single value selected in the "Affected Computer" custom field. The global format, supporting any number of values in the "Affected Computer" custom field is:
object HAVING inR(Key IN (${Affected Computer${0}}))Replacing the '=' with 'IN (...)' and adding the index ${0} to the placeholder will indicate ANY value in the "Affected Computer" whether one or multiple.