Jira プロジェクトとは

Your work item tracker should be the hub of your development project. When properly configured, Jira helps your team members prioritize and organize work better, so they can spend more time developing great software instead of wrangling work items.

A project is simply a collection of work items (stories, bugs, tasks, etc). You would typically use a project to represent the development work for a product, project, or service in Jira.

スクラム、カンバン、バグ トラッキングの違い 

• 　スクラムはイテレーションを基準にした手法で、一般的にはチームでの製品開発プロジェクトに向いています。具体的にはチームが新しいバージョンを定期的にリリースする場合は、スクラムがフィットするでしょう。 

• かんばんは継続的作業フローに効果的です。(サービス重視のチームなど) 制限に基づいた手法をすることで、チームが過負荷にならずに作業を進めていくことができます。

• バグ トラッキングは、新機能やバグを追跡するための基本的なワークフローを提供します。

Team-managed software projects

Our team-managedScrum and Kanban projects are great for teams who are new to agile. Get your team up-and-running with this simplified board-view project template. The set-up is straight-forward and streamlined, delivering more power progressively as you need it. Anyone can create these, while only administrators can create company-managed projects.

はじめる前に

You should be a Jira administrator (i.e. someone with the Administer Jira global permission), if you want to set up a new project in Jira (excluding team-managed project templates — unless your Jira admin has implemented a permission scheme in which only admins can create agility projects). Many of the tasks involved can only be performed by a Jira administrator, such as creating a project, modifying a workflow, etc. For more information, see Permissions overview.

The topics in this section cover the activities that you will need to do when configuring a project:

プロジェクトの作成

Your first task is to create a Software project and configure it according to the needs and requirements of your development team. You need to be a Jira admin to create a project (excluding team-managed project templates — unless your Jira admin has implemented a permission scheme in which only admins can create agility projects), but you can configure most project details if you are a project admin.

Find out more: Configuring projects

プロジェクト ボードの設定

A board is the central tool for working with work items in a Scrum or Kanban development project. A Scrum or Kanban board will be created when you create a Scrum or Kanban development project respectively. You can add more boards of either type to the project, if you like.

Find out more: Configuring a board

プロジェクト権限の設定

You can control access to your project by configuring a permission scheme. A permission scheme maps users, user groups, roles, etc to the project functions (e.g. Assign work items). Your new project will be pre-configured with the default permission scheme.

Learn more: Managing project role memberships

Tweak work types, workflow, screens, and fields 

Your project is pre-configured with work types, a workflow, screens, and fields. You can change these to suit any development process. For example, you may want to create a 'Design' work type or add a 'QA review' step to your workflow.

Find out more: Defining work type field values, Workflows, Defining a screen, Jira custom fields

コンポーネントの作成

Components can be used to group work items in a project. However, in an agile project, you should consider using epics to group work items (stories) instead, as there are more features that support working with epics, like the epic column on boards, reports, etc.

Find out more: Managing components