Jira アプリケーションとプロジェクト タイプの概要
The Jira family of applications are built to deliver a tailored experience to their user. Jira Core is the default application of Jira, and will always be present in a Jira instance. You may also choose to include other applications in your instance, such as Jira Software or Jira Service Management. A user may require access to one, all, or any combination of these applications.
Note that as Jira Core is the default application, if you have a license for Jira Software or Jira Service Management, your users automatically have access to Jira Core without requiring an additional license. For example, a Jira Software user can view development information on an agile board, and can also view business projects.
アプリケーションの特徴とプロジェクト タイプ
各アプリケーションはユーザーの必要に応えるエクスペリエンスを提供するとともに、関連付けられたプロジェクト タイプを持ち、また、それに応じたアプリケーション特有の機能を提供します。下記は、プロジェクト タイプとそれぞれに関連付けられたアプリケーション特有の機能を一覧表示したものです。
| アプリケーション | プロジェクト タイプ | アプリケーション特有の機能セット |
|---|---|---|
Jira Core |  ビジネス プロジェクト |
|
Jira Software |  ソフトウェア プロジェクト |
|
Jira Service Management |
|
|
アプリケーションの機能とユーザー
All users that can log in to a Jira instance will be able to see all the projects in that instance (pending permissions), but they will only be able to see the application-specific features when they have application access. For example, a Software project is able to display information from linked development applications, such as Bitbucket and FishEye on a Software project, and you can create agile boards, but this information is only viewable by a Jira Software user. A Jira Core user would be able to see the Software project, but would not be able to see the application-specific features, like agile boards or development information. Likewise, a Jira Software user would not be able to see any Jira Service Management application-specific features on a service project — only a basic view of the project and its issues.
- Only a Jira administrator can create a project for an installed application. They do not need application access to create the project, but they do need application access if they'd like to view or use the project.
- Anonymous users will have access equivalent to Jira Core users. In other words, they can view issues and work in any type of project, but they won't see application-specific features, e.g. agile boards, which are Jira Software-specific features. To know how to allow anonymous users access to projects, see Allowing anonymous access to your instance.
アプリケーションの一覧、アプリ毎のユーザーのロール、プロジェクトアプリ特有の機能は以下の通りです。
Jira Core | Jira Software | Jira Service Management | |||
|---|---|---|---|---|---|
| jira-core-user | jira-software-user | jira-servicedesk-agent | |||
ビジネス プロジェクト | プロジェクト レベル | ビュー |  | | |
| 課題レベル | 作成 | | | | |
| ビュー | | | | ||
| コメント | | | | ||
| トランジション | | | | ||
Jira Gadgets | ビュー | | | | |
ソフトウェア | プロジェクト レベル | ビュー | | | |
| 課題レベル | 作成 | | | | |
| ビュー | | | | ||
| コメント | | | | ||
| トランジション | | | | ||
| 開発情報の表示 | | | | ||
| リリース情報の表示 |  | | | ||
| ボード レベル | 作成 | | | | |
| ビュー | | | | ||
| Jira Software ガジェット | ビュー | | | | |
サービス | プロジェクト レベル | ビュー | | | |
| 課題レベル | 作成 | | | | |
| ビュー | | | | ||
| コメント | | | | ||
| トランジション | | | | ||
| SLA レベル | 作成 | | | | |
| ビュー | | | | ||
| キュー レベル | 作成 | | | | |
| ビュー | | | | ||
Jira Service Management ガジェット | ビュー | | | |