Jira Work Items Tutorial
In this tutorial, we'll explain how to work with work items in Jira. Note that the team rituals you do outside Jira - like sprint planning meetings, retros, and daily standups - won't be covered here. You can read up on those in How to do scrum with Jira.
所要時間:
読む時間 10 分。
対象者:
Jira を初めて使用するため、実際に何をすべきかわからないユーザー
前提条件:
- Jira アカウントを作成していること
-
Jira プロジェクトを作成していること
In Jira, teams use work items to track individual pieces of work that must be completed. Depending on how your team uses Jira, a work item could represent a project task, a helpdesk ticket, a leave request form, etc. In Jira, work items typically represent things like big features, user requirements, and software bugs.
Create a work item
There are a few different ways to create work items:
Jira 内の任意の場所のトップ ナビゲーション バーから

バックログでの操作
ボード上で (チーム管理対象プロジェクトのみ)
任意: サブタスクの作成
Work items can also have sub-tasks that are assigned and tracked individually. You might create sub-tasks for any of the following reasons:
- To split a work item into even smaller chunks
- To allow various aspects of a work item to be assigned to different people
- To create a to-do list for a work item
サブタスクを作成する手順は、次のとおりです:
- Navigate to a work item, and select more ( ••• ) > Create Sub-Task.
- 必要な詳細を入力し、[作成] をクリックします。
Estimating work items in your backlog helps you to predict how long portions of the backlog might take to be delivered.
Why estimate work items? Estimation is all about velocity.The primary purpose of applying estimates backlog items is to use that information to work out how long it will take to deliver portions of the backlog.
従来の開発チームでは、マネージャーは「工数」で項目を見積もっていました。そして、プロジェクトのバックログで工数を合計して、チームの人数と週時間数で割り、完了予想日を割り出します。もちろん、こうした見積は、多くの場合、見積の際に (過大または過小な見積に傾く) チームが持つ自然な傾向や、予期しない中断、作業期間中のチームのパフォーマンスの改善などを考慮に入れていないため、非常に精度が低いことが判明しました。
So in the Scrum world, most teams don't try to achieve estimation accuracy; instead they aim to achieve a reliable velocity. Velocity is a measure of the number of estimation units that a team tends to complete from sprint to sprint. After their first few sprints, most teams will achieve a reasonably consistent velocity. Armed with velocity and estimates on backlog work items, teams can predict how long portions of the backlog will take to complete.
たとえば、各スプリントにおけるチームの「工数」キャパシティが 120 時間で、ベロシティが 60 時間であった場合、60 時間のベロシティを、バックログの一部を完了するスプリント数を見積もるために使用できます。その場合、「他の 60 時間」はどうなったのか、チームの生産性が低いのかと気にしてしまいがちです。しかし、問題はない場合の方が多いのです。チームの見積もりとは、項目がどれほど難しいものになるかという観点を示すもので、チームの自然な行動 (たとえば高すぎるまたは低すぎる見積もり) や組織的なオーバーヘッドに影響されます。計画策定の観点から言えば、大事なのはベロシティのみです。
Most teams estimate using story points. Story points measure the complexity of one work items relative to others. This makes sense because the main questions to be answered are 'How much work can we realistically commit to completing this sprint?' and 'How long will this part of the backlog take to deliver?'. A story point approach can deliver the answers to these questions without the anxiety around 'accuracy' that teams feel when asked to estimate in hours.
見積もりとベロシティの追跡方法に関して詳しくは、バーンダウン チュートリアルをご覧ください。
To set an estimate for a work item:
- 見積もりを入力します。
入力後に見積もりを変更できますか?簡単に言えばできますが、スプリントが開始された後で見積もりの値を変更すると、バーンダウン チャートではスコープの変更として表示されます。
If you're finding it hard to estimate work items, that's totally normal! Check out our estimation guide for tips and tricks on finding the right estimates for your work items.
Rank your work items in order of priority
Ranking your work items in order of priority allows the team to see which work items they'll be working on next. To rank your work items, navigate to your backlog or board and click-and-drag your work items to order than based on priority. Here are some examples of where you might do this:
-
In a Scrum project, when planning your next sprint you might rank the work items in your backlog, and then decide to put the first 10 (or however many work items the team is capable of completing) into the sprint.
-
In a Kanban template, you might rank the work items in the To do column, and have team members take a work item off the top of the list when they need more work to do. With this approach, the column with all To do work items will need constant attention as priorities shift.
Note: You must have the Schedule Work Item and Edit Work Item permissions for the work item you want to move higher or lower on your board.
Flag a work item
You have the option to flag a work item, which look like this:
Flagging a work item is useful because it encourages collaboration and communication throughout the team. Here are some examples:
-
You're working on a task, but realize you don't have capacity to finish it off. You can flag the work item, and a team member with spare capacity who looks at the board can jump on and help.
-
A work item you're working on becomes blocked. You can flag the work item, add a comment explaining the blocker, and move on to the next task. Anyone who looks at the board will see that it has been flagged, and understand what's going on when they open it.
To flag a work item:
-
ボードに移動します。
-
Right click a work item.
-
[フラグの追加] をクリックします。
Transition work items
Transitioning work items shows progress across your workflow. To transition a work item from one column to another, drag a work item and place it in its new column.
Note that if you find that you're not able to transition a work item into another column, it may be because the workflow for your project is restricting you from doing so. What makes Jira so powerful is that administrators can enforce certain rules on the project's workflow, like forcing bugs to go through a QA column, or not allowing Stories to go straight from To do to Done. For more information, check out our workflow documentation.
Filter work items
A work item filter allows you to hide the work items you don't want to see, and zone in on the ones you want to focus on. Jira has Quick filters, which allow you to filter the work items on your board. Here's what they look like on Scrum/Kanban boards:
-
Search bar: Display work items that contain a search term, and hide the rest.
-
Quick filters menu: By default, you can filter by work items assigned to you, and work items recently updated. Any Quick filters you create will also display here.
-
Assignee menu: Only display work items assigned to people you select.
独自のクイック フィルター (スクラム ボードとカンバン ボード) を作成するには:
- 省略符号ボタン対象のボードに移動し、[その他] (
) > [ボード設定] を選択します。
- クイックフィルタータブをクリックします。
-
フィルターの名前、JQL クエリ、および説明を入力します。JQL に関する詳細は、高度な検索ドキュメントをご覧ください。
-
[追加] をクリックします。
自動化を秘密兵器として使う
Jira is the place where work lives. Sometimes a lot of work can live there! Automation is the key to keeping all work items up to date and in order. See the most commonly used automations in the Jira automation template library.
その他の必要情報
For more detailed information on working with work items in Jira, check out our documentation on work items. Excited to get started? Check out our free Jira templates.
ご質問はこちらまで。アトラシアンコミュニティ