Jira Core の構成要素
Jira Core is a Jira application that provides you with a workflow management system that you can use for many things, including running projects, tracking assets, and basically anything that requires work moving through a workflow. Jira Core can be customized to suit your needs, and can also be extended and linked with other applications to provide you with the perfect solution to track all your work in one place.
Understanding the basics of Jira Core will help you get the most out of your application. This page will explain the core terminology and functionality that makes Jira Core the application you need to help you manage your work efficiently.
準備ができましたか？基本的な概念を習得しましょう。
| |
|---|---|
| 無料トライアルにサインアップ | |
課題
Issues are the work packets in Jira Core. Each issue can be further defined by assigning the issue an issue type. For example, if you're running a project in an office, issues could represent the tasks you need to do to complete that project. Each issue type would be a type of task, like administration task, filing task, or create document task. If you're using Jira Core for asset tracking, an issue could represent an asset (or inventory item) and the issue type could be the types of assets (laptops, monitors, printers etc.). Issues then progress (or move) through Jira Core via an associated workflow that dictates what can and can't (or more correctly, what should and shouldn't!) happen to that issue.
So how do I group issues? What if I want a construction project, and I also want to track my assets for that project in Jira Core, how can I do that? Well, you use projects!
プロジェクト
"プロジェクト"は課題をまとめる方法の一つです。既定設定を適用するとします。既定設定では必ず、すべての課題にワークフローを通して進捗を確認するための情報があります。それぞれのプロジェクトには管理者がいます。基本的にはプロジェクトリードでプロジェクトの管理をする責任がある人です。
Jira Core users may work with issues in one or several projects, and would complete the work required to progress the issues through their workflows.
よくできました！課題が作業であり、プロジェクトに属していることがわかりましたね。しかし、どのようなワークフローで、どのように課題に影響するのでしょうか？
ワークフロー
Workflow dictates how an issue can be progressed in a project. The workflows can be as simple or as complex as you need them. Workflows are often modeled on existing processes, and are made up of statuses (or steps) and transitions (movements between statuses). When you create an issue, it will automatically be assigned a workflow and a status on that workflow. Where it can move to is defined by the transitions that exit that status. An example of the default workflow that ships with Jira Core is shown below:
Jira アプリケーション
Jira Core is one of several Jira applications. Each application has its own distinct features that makes it suitable for servicing the market it's designed for. For example, Jira Software is designed for agile software developers, and its features include agile boards, software specific project types, and better integration points with other developer tools.
You may have access to more than just the Jira Core application, and you can view this list of applications and feature access to gain a better understanding of the power of Jira!
So that's the basics. Jira Core is functional straight 'out of the box', but if you think you'll need to know a little more, to get some ideas on what you could do, take a look at this guide to see what's possible with Jira Core.