Commit 7a08456e authored by Phil Hughes's avatar Phil Hughes

Updated issue boards docs

parent 110cd589
...@@ -31,7 +31,6 @@ Below is a table of the definitions used for GitLab's Issue Board. ...@@ -31,7 +31,6 @@ Below is a table of the definitions used for GitLab's Issue Board.
There are three types of lists, the ones you create based on your labels, and There are three types of lists, the ones you create based on your labels, and
two default: two default:
- **Backlog** (default): shows all issues that do not fall in one of the other lists. Always appears on the very left.
- **Done** (default): shows all closed issues. Always appears on the very right. - **Done** (default): shows all closed issues. Always appears on the very right.
Label list: a list based on a label. It shows all issues with that label. Label list: a list based on a label. It shows all issues with that label.
- Label list: a list based on a label. It shows all opened issues with that label. - Label list: a list based on a label. It shows all opened issues with that label.
...@@ -58,7 +57,7 @@ have the right [permissions](#permissions). ...@@ -58,7 +57,7 @@ have the right [permissions](#permissions).
## First time using the Issue Board ## First time using the Issue Board
The first time you navigate to your Issue Board, you will be presented with the The first time you navigate to your Issue Board, you will be presented with the
two default lists (**Backlog** and **Done**) and a welcoming message that gives a default list (**Done**) and a welcoming message that gives
you two options. You can either create a predefined set of labels and create you two options. You can either create a predefined set of labels and create
their corresponding lists to the Issue Board or opt-out and use your own lists. their corresponding lists to the Issue Board or opt-out and use your own lists.
...@@ -93,23 +92,20 @@ in the list's heading. A confirmation dialog will appear for you to confirm. ...@@ -93,23 +92,20 @@ in the list's heading. A confirmation dialog will appear for you to confirm.
Deleting a list doesn't have any effect in issues and labels, it's just the Deleting a list doesn't have any effect in issues and labels, it's just the
list view that is removed. You can always add it back later if you need. list view that is removed. You can always add it back later if you need.
## Searching issues in the Backlog list ## Adding issues to lists
The very first time you start using the Issue Board, it is very likely your You can bulk add issues to a list by clicking the **Add issues** button.
issue tracker is already populated with labels and issues. In that case, This opens up a modal window where you can select multiple issues and then
**Backlog** will have all the issues that don't belong to another list, and add these issues to the selected list. By default the first list is selected,
**Done** will have all the closed ones. but this can be changed in the dropdown menu next to the **Add issues** button
in the modal.
For performance and visibility reasons, each list shows the first 20 issues Within this modal you can also issues. This is done by using the filters at the
by default. If you have more than 20, you have to start scrolling down for the top of the modal.
next 20 issues to appear. This can be cumbersome if your issue tracker hosts
hundreds of issues, and for that reason it is easier to search for issues to
move from **Backlog** to another list.
Start typing in the search bar under the **Backlog** list and the relevant You can filter by author, assignee, milestone and label.
issues will appear.
![Issue Board search Backlog](img/issue_board_search_backlog.png) ![Bulk adding issues to lists](img/issue_boards_add_issues_modal.png)
## Filtering issues ## Filtering issues
...@@ -142,8 +138,8 @@ A typical workflow of using the Issue Board would be: ...@@ -142,8 +138,8 @@ A typical workflow of using the Issue Board would be:
and gets automatically closed. and gets automatically closed.
For instance you can create a list based on the label of 'Frontend' and one for For instance you can create a list based on the label of 'Frontend' and one for
'Backend'. A designer can start working on an issue by dragging it from 'Backend'. A designer can start working on an issue by dragging adding it to the
**Backlog** to 'Frontend'. That way, everyone knows that this issue is now being 'Frontend' list. That way, everyone knows that this issue is now being
worked on by the designers. Then, once they're done, all they have to do is worked on by the designers. Then, once they're done, all they have to do is
drag it over to the next list, 'Backend', where a backend developer can drag it over to the next list, 'Backend', where a backend developer can
eventually pick it up. Once they’re done, they move it to **Done**, to close the eventually pick it up. Once they’re done, they move it to **Done**, to close the
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment