Configuring a project
Your issue tracker should be the hub of your development project. When properly configured, Jira Software helps your team members prioritize and organize work better, so they can spend more time developing great software instead of wrangling issues.
A project is simply a collection of issues (stories, bugs, tasks, etc). You would typically use a project to represent the development work for a product, project, or service in Jira Software.
Scrum, Kanban, Bug tracking, or agility*?
- Scrum has an iteration-based approach, which is generally a good fit for teams developing products, particularly if your team is releasing new versions on a regular schedule.
- Kanban is better suited for a continuous flow of work (e.g. service-oriented teams), where its constraint-based approach helps prevent your team from being overloaded.
- Bug tracking delivers a basic workflow for tracking new features and bugs.
- Agility* delivers a simplified board-view project template which is straight-forward and streamlined, providing more power progressively as you need it.
*Beta development phase. We're still adding features to the agility board.
Before you begin
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 Software (excluding agility 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.