Summary Files Commits Branches @commit @diff @stats
path: root / src / tutorials / how-to-use-jira / projects.md
diff options
context:
space:
mode:
1 files changed, 26 insertions, 26 deletions
-rw-r--r--src/tutorials/how-to-use-jira/projects.md52
diff --git a/src/tutorials/how-to-use-jira/projects.md b/src/tutorials/how-to-use-jira/projects.md
index cfe2e0e..4a9cea7 100644
--- a/src/tutorials/how-to-use-jira/projects.md
+++ b/src/tutorials/how-to-use-jira/projects.md
@@ -15,33 +15,33 @@
In short, **projects are a collection of issues** with added functionality for **organising them, getting statistics, etc**.
-![](./img/projects.png)
+![](./img/projects.webp)
## Creating a project
To create a project, either **click on `Create project` from the menu `Projects` in the top bar**,
-![](./img/create-project-top.png)
+![](./img/create-project-top.webp)
or **click on the `Create project` button in the `View all projects` page**.
-![](./img/view-all-projects-top.png)
+![](./img/view-all-projects-top.webp)
-![](./img/create-project.png)
+![](./img/create-project.webp)
**Note**: when you **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 **won't be covered**.
-![](./img/choose-project-type.png)
+![](./img/choose-project-type.webp)
After that you'll need to put a **name** for your project, set a **key** (used as an ID for issues ; it is automatically generated, but you can change it if you want) and select a **template**.
-![](./img/create-project-new.png)
+![](./img/create-project-new.webp)
This tutorial covers **only** the three classic software templates: [**Kanban**](./kanban.html), [**Scrum**](./scrum.html) and [**Bug tracking**](./bug.html).
-![](./img/choose-classic-template.png)
+![](./img/choose-classic-template.webp)
In a nutshell, **templates** govern how **boards and issues should work together**. Later in the tutorial we cover the differences between these templates.
@@ -55,11 +55,11 @@ Each project contains, amongst many other things, boards. **Boards are a way to
**Boards are divided into columns** that contain the cards (issues). A card can move **freely** from one column to another.
-![](./img/SOD.png)
+![](./img/SOD.webp)
To illustrate how this could be useful, let's say we have three columns: `TO DO`, `DOING` and `DONE`.
-![](./img/todo-doing-done.png)
+![](./img/todo-doing-done.webp)
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.
@@ -67,9 +67,9 @@ Of course, the name, quantity and purpose of different columns **depend on the p
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/board-settings.png)
+![](./img/board-settings.webp)
-![](./img/columns-edit.png)
+![](./img/columns-edit.webp)
### Adding more boards to a project
@@ -77,31 +77,31 @@ You can also add to a project as many [**Scrum**](./scrum.html) and [**Kanban**]
This can be done, either while in a board, from **clicking the three dots and choosing `Create board`**
-![](./img/create-board.png)
+![](./img/create-board.webp)
or **in the sidebar, from the `Board` menu**.
-![](./img/sidebar-create-board.png)
+![](./img/sidebar-create-board.webp)
After that, you are met with the `Create a board` window, where you can choose your template.
-![](./img/scrum-kanban-board.png)
+![](./img/scrum-kanban-board.webp)
Once you've made your choice, you will be met with three options:
-![](./img/board-from.png)
+![](./img/board-from.webp)
- **Board created with new Software project** - creates a new project with a new board (has the name of the project).
- ![](./img/npb.png)
+ ![](./img/npb.webp)
- **Board from existing project** - creates a board that gets the filter from another project
- ![](./img/ntb.png)
+ ![](./img/ntb.webp)
- **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/ntb-filter.png)
+ ![](./img/ntb-filter.webp)
## Backlog
@@ -109,11 +109,11 @@ Once you've made your choice, you will be met with three options:
Depending on your project template, the backlog will either be a **separate window ([Scrum](./scrum.html))**,
-![](./img/scrum-backlog.png)
+![](./img/scrum-backlog.webp)
**just a column in a board ([Kanban](./kanban.html))**,
-![](./img/backlog-kanban.png)
+![](./img/backlog-kanban.webp)
or **nonexistent ([bug tracking](./bug.md))**.
@@ -123,23 +123,23 @@ The purpose of the backlog depends on the template and it is described in the pa
**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/add-item-kanban.png)
+![](./img/add-item-kanban.webp)
From here you can **add a website shortcut**, simply by putting the web address and giving it a name.
-![](./img/add-item-to-project.png)
+![](./img/add-item-to-project.webp)
-![](./img/add-shortcut.png)
+![](./img/add-shortcut.webp)
The name is used for showing the shortcut on the sidebar.
-![](./img/added-site.png)
+![](./img/added-site.webp)
You can also add a `Bitbucket` or `GitHub` repository which you can **leave** only as a **shortcut**, or you can **integrate** it so that **issues are transferred to Jira**.
-![](./img/test-repo.png)
+![](./img/test-repo.webp)
-![](./img/test-repo-sidebar.png)
+![](./img/test-repo-sidebar.webp)
**Integration won't be covered in this tutorial**, but I can recommend [this](https://www.idalko.com/jira-github-integration/) article for `GitHub` integration and [this](https://www.idalko.com/jira-bitbucket-integration/) one for `Bitbucket` integration.