Jira Service Management: Escalations

Jira Service Management 評価用リソース

このページの内容

お困りですか?

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

コミュニティに質問

目的

What are the best practices to manage escalations in Jira Service Management?

環境

サーバー版/クラウド版

方法

Escalations in Jira Service Management:

Because our Jira products are highly configurable, you can design your workflow and processes in ways that work for your team. You can manage escalations in Jira Service Management in a variety of ways:

  • Create a queue for escalations. The queues within each service project can be configured to capture issues based on any type of criteria. You can add an Escalations custom field for your agents to populate, or you could create a component or label to use for escalations. Then, you would have the option to create a new queue for escalations using the escalations custom field or tag. You could even apply an escalations SLA to determine escalation time or create a custom automation rule to send an email to an agent managing escalations when the field is toggled or when a tag is added.
     
  • Create a status within your workflow for escalations. You also have the option to build an 'Escalated' status into a service project workflow. A queue can capture any issues in that status, and your escalation agents can work from that queue. You can build any number of statuses into your workflows, such as 'Escalated to Tier 2', 'Escalated to Tier 3', 'Escalated to Tech Support', or any number of statuses that queues can query against.

  • Issue mentions. Agents could @mention a higher tier agent, who can comment on the issue internally or publicly, depending on how you want to manage this. A mention would send the mentioned agent an email notification. Your agents can also assign issues directly to higher tier agents depending on the workflow that you outline for your team

Escalations between Jira Service Management and Jira Software/Jira Core:

If you are using Jira Service Management alongside a project management Jira product such as Jira Software and Jira Core, then you can allow Jira Service Management agents to escalate to other Jira teams if those products are installed on the same platform. 

  • A Jira Service Management agent creates a linked issue in Jira Software. See escalate Jira Service Management issues to other Jira teams from our best practices for software teams using Jira Service Management guide (available for both Server and Cloud).

  • A Jira Service Management agent @mentions a Jira Software user on a Jira Service Management request. When Jira Service Management and Jira Software are on the same platform, you can add Jira Software users as collaborators on Jira Service Management requests. For a more informal escalation, you could allow the Jira Software collaborator to internally comment on a Jira Service Management issue when mentioned. 




最終更新日 2020 年 11 月 9 日

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

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