課題タイプ

Issue types distinguish different types of work in unique ways, and help you identify, categorize, and report on your team’s work across your Jira site. They can help your team build more structure into your working process. 

複数の課題タイプを使用すると、チームが取り組む作業の検索および並び替え、特定のタイプの作業の進捗の追跡、バグに対するチームの対応状況およびより大きなイニチアチブの完了速度の見積もりに役立ちます。

Each Jira product comes with default issue types to suit the needs of your projects and teams. You can customize your issue types to match any method of project management you want.

We provide suggested issue types to help you classify tasks to work in common agile software development or IT service management methods. Get started with these default issue types or create your own.

What are parent, standard, and child issues?

Depending on the complexity of the projects you track in Jira, you may want to group or nest different work items hierarchically. This can help your teams sweat the details on individual tasks while Scrum masters, project managers, or other team leaders track your team's bigger picture.

 By default, Jira supports three levels of hierarchy:

  • Parent issues (or epic issues) represent high-level initiatives or bigger pieces of work in Jira. For software teams, a parent issue (or epic issue) may represent a new feature they're developing. For IT service teams, parent issues may represent a major service change or upgrade. For business teams, parent issue may represent major deliverables or phases of a project.
  • Standard issues represent regular business tasks. In Jira, standard issues are where daily work is discussed and carried out by team members. For software teams, standard issues (like bugs or stories) estimate and track the effort required to build an interaction or other end goal in your team's software. For service teams, standard issues represent different requests made by your team's customers, like requesting service or support, or reporting problems or incidents with your infrastructure. For business teams, standard issues represent and track your team member's daily tasks.
  • When needed, child issues (or subtask issues) can help your team break a standard issue into smaller chunks. This can be helpful if your team underestimates the scope or complexity of their work. Child issues (or subtask issues) can be described and estimated separately to their related standard issue and can help your team better understand and estimate similar work in the future.

Default issue types

各 Jira 製品で提供される既定の課題タイプの一覧は次のとおりです。

Jira Core (ビジネス プロジェクト) の課題タイプ

By default, business projects come with one standard issue type:

タスク

タスクは、実施すべき作業を表しています。



By default, business projects come with one child issue type:

サブタスク

サブタスクは、タスクの完了に必要な個々の作業です。

Jira Software (ソフトウェア プロジェクト) の課題タイプ

By default, software projects come with one parent issue type:

エピック

A big user story that needs to be broken down. Epics group together bugs, stories, and tasks to show the progress of a larger initiative. In agile development, epics usually represent a significant deliverable, such as a new feature or experience in the software your team develops.


By default, software projects come with three standard issue types:

バグ

バグとは、プロジェクトの機能が損なわれる、または機能しなくなる問題のことです。

ストーリー

ユーザーストーリーは、実施すべき最小作業単位です。

タスク

タスクは、実施すべき作業を表しています。


By default, software projects come with one child issue type:

サブタスク

A subtask is a piece of work that is required to complete a task. Subtasks issues can be used to break down any of your standard issues in Jira (bugs, stories or tasks).

Jira Service Desk (サービス デスク プロジェクト) の課題タイプ

変更

現在の IT プロファイルの変更をリクエストします。

IT help

IT 関連の問題のヘルプをリクエストします。

インシデント

インシデントまたは IT サービスの停止を報告します。

新機能

新機能またはソフトウェア機能をリクエストします。

問題

複数のインシデントの根本原因を調査および報告します。

サービス リクエスト

社内またはカスタマー サービス デスクからヘルプをリクエストします。

承認付きのサービス リクエスト

マネージャーまたは役員による承認が必要なヘルプをリクエストします。

サポート

カスタマー サポートの課題に関するヘルプをリクエストします。 

最終更新日 2020 年 6 月 29 日

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

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