Jira Service Management: Projects vs Queues

Jira Service Management 評価用リソース

このページの内容

お困りですか?

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

コミュニティに質問

 


目的

What's the best practice for deciding what is a queue and a project in Jira Service Management?

環境

サーバー版/クラウド版

方法

In Jira Service Management, deciding what is a queue and a project depends on how you work and how you organize your teams. If you have multiple departments, and they should not be able to access tickets outside their department, we would go with a separate project for each department and configure project permissions to restrict access. If you have one team that supports multiple products, you could potentially run this out of the one project and set up a separate queue for reach product. That way, the support team need not have to navigate to different projects to view all the tickets.

追加情報

With a single license of Jira Service Management, you are free to create as many projects as you like at no extra cost. Queues are to parse issues within a project to better prioritize and route them. For example, an IT team would work on a single project with multiple queues like Hardware Request, Password Reset, Software Request etc. Another team might work in a separate project for receiving requests from your businesses customers with queues for Feature Requests, Bug Reports, and Usage Queries.






最終更新日 2020 年 11 月 9 日

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

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