Service Management Agents will be treated as customers by Jira Service Management

お困りですか?

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

コミュニティに質問

プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Fisheye および Crucible は除く

問題

Sometimes Jira Service Management notification, automation and SLA don't work as expected for example:

SLA

If SLA Comment:For Customer condition is used to stop the SLA. It will not be triggered if an Agent add any comment in Jira and share it with Customer.

通知

Jira Service Management agents don't receive notifications of internal comments, even when @mentioned on the issue as discussed in here.

自動化

Automation does not trigger when some condition is used.

Example in:

JSDSERVER-3390 - 課題情報を取得中... ステータス

In the above example, the automation did not run since it did not match User is not a customer condition.

原因

Based on the problem above, the cause of it is because Service Management Agents are treated as a customer persona and not as an Agent if one of below is met:

  • The Agent is the issue reporter.
  • The Agent is a request participant on the ticket.
  • The Agent is a member of the organization which the ticket is shared with.
  • The Agent is an approver of the request.

This is an expected behavior for Jira Service Management. If an agent is added in one of the above roles, it will automatically take on the customer persona.


説明
製品Jira Service Management

最終更新日: 2024 年 1 月 8 日

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

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