'def title Projects - How to use Jira 'def desc Projects are a collection of issues with added functionality for organising them, getting statistics, etc. # {title} {pagenav 4 min;24 July 2020;03 June 2021} {pagination ./;Cards;./cards.html;Kanban template;./kanban.html} :contents :numbered 1. {uhref Creating a project} 2. {uhref Boards} .numbered 1. {uhref Columns} 2. {uhref Adding more boards to a project} 3. {uhref Backlog} 4. {uhref Add item} In short, {b projects are a collection of issues} with added functionality for {b organising them, getting statistics, etc}. {img ./img/projects.png} ## Creating a project To create a project, either {b click on {` Create project} from the menu {` Projects} in the top bar}, {img ./img/create-project-top.png} or {b click on the {` Create project} button in the {` View all projects} page}. {img ./img/view-all-projects-top.png} {img ./img/create-project.png} {b Note}: when you {b have created your account} the first thing you'll see is the {` Create project} page. You'll be met by the {` Choose project type} screen. From here choose {` Classic project}, in this tutorial the {` Next-gen project} types {b won't be covered}. {img ./img/choose-project-type.png} After that you'll need to put a {b name} for your project, set a {b key} (used as an ID for issues ; it is automatically generated, but you can change it if you want) and select a {b template}. {img ./img/create-project-new.png} This tutorial covers {b only} the three classic software templates: {b {url Kanban;./kanban.html}}, {b {url Scrum;./scrum.html}} and {b {url Bug tracking;./bug.html}}. {img ./img/choose-classic-template.png} In a nutshell, {b templates} govern how {b boards and issues should work together}. Later in the tutorial we cover the differences between these templates. Projects also have {url Releases;./releases.html}, {url Pages;./pages.html} and {url Components;./components.html}, that are also explored. ## Boards Each project contains, amongst many other things, boards. {b Boards are a way to better organise results from {url filters;./filters.html}}. By default every project gets a board with a filter for all of the project's issues. ### Columns {b Boards are divided into columns} that contain the cards (issues). A card can move {b freely} from one column to another. {img ./img/SOD.png} To illustrate how this could be useful, let's say we have three columns: {` TO DO}, {` DOING} and {` DONE}. {img ./img/todo-doing-done.png} When you create an issue you initially put it in the {` TO DO} column. After someone has started working on it, they put the issue in the {` DOING} column. Finally, when the issue is resolved, it is put in the {` DONE} column. Of course, the name, quantity and purpose of different columns {b depend on the project's organisation}. Adding and removing columns can be done from the {` Columns} tab in the {` Board settings} menu (three dots on the top right of a board). {img ./img/board-settings.png} {img ./img/columns-edit.png} ### Adding more boards to a project You can also add to a project as many {b {url Scrum;./scrum.html}} and {b {url Kanban;./kanban.html}} templated boards as you want. This can be done, either while in a board, from {b clicking the three dots and choosing {` Create board}} {img ./img/create-board.png} or {b in the sidebar, from the {` Board} menu}. {img ./img/sidebar-create-board.png} After that, you are met with the {` Create a board} window, where you can choose your template. {img ./img/scrum-kanban-board.png} Once you've made your choice, you will be met with three options: {img ./img/board-from.png} :unordered - {b Board created with new Software project} - creates a new project with a new board (has the name of the project). {img ./img/npb.png} - {b Board from existing project} - creates a board that gets the filter from another project {img ./img/ntb.png} - {b Board from an existing Saved Filter} - as it says, you add to the project (indicated in the {` Location} field) a board based on a saved filter {img ./img/ntb-filter.png} ## Backlog {b The backlog is a place for issues that outline a general task/feature}. Depending on your project template, the backlog will either be a {b separate window ({url Scrum;./scrum.html})}, {img ./img/scrum-backlog.png} {b just a column in a board ({url Kanban;./kanban.html})}, {img ./img/backlog-kanban.png} or {b nonexistent ({url bug tracking;./bug.md})}. The purpose of the backlog depends on the template and it is described in the page of each template. ## Add item {b You can also add some resources to the sidebar of your project} for everyone to use. That is done through the {` Add Item} menu. {img ./img/add-item-kanban.png} From here you can {b add a website shortcut}, simply by putting the web address and giving it a name. {img ./img/add-item-to-project.png} {img ./img/add-shortcut.png} The name is used for showing the shortcut on the sidebar. {img ./img/added-site.png} You can also add a {` Bitbucket} or {` GitHub} repository which you can {b leave} only as a {b shortcut}, or you can {b integrate} it so that {b issues are transferred to Jira}. {img ./img/test-repo.png} {img ./img/test-repo-sidebar.png} {b Integration won't be covered in this tutorial}, but I can recommend {url this;https://www.idalko.com/jira-github-integration/} article for {` GitHub} integration and {url this;https://www.idalko.com/jira-bitbucket-integration/} one for {` Bitbucket} integration. From the {` Add Item} menu you can also {b toggle the shortcut to {url Pages;./pages.html}}.