Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
0b201c56
Commit
0b201c56
authored
Jun 28, 2017
by
Marcia Ramos
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
add use-cases for boards w/ milestones and focus mode
parent
bb1a438a
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
20 additions
and
2 deletions
+20
-2
doc/user/project/issue_board.md
doc/user/project/issue_board.md
+20
-2
No files found.
doc/user/project/issue_board.md
View file @
0b201c56
...
...
@@ -28,6 +28,14 @@ empowered with the ability to create multiple boards per project.
## Use-cases
There are inumerous use-cases for the use of Issue Boards, we will just
exemplify with a couple situations, but the possilities go where our creativity goes.
For a broader use-case, please check the blog post
[
GitLab Workflow, an Overview
](
https://about.gitlab.com/2016/10/25/gitlab-workflow-an-overview/#gitlab-workflow-use-case-scenario
)
.
### Single Board
GitLab Workflow allows you to discuss proposals in issues, categorize them
with labels, and and from there organize and prioritize them with Issue Boards.
...
...
@@ -44,6 +52,8 @@ beginning of the dev lifecycle until deployed to production
-
Prioritize the issues in a list by moving them vertically
-
Move issues between lists to organize them according to the labels you've set
### Multiple Boards
To enhance the workflow exemplified above, with
[
Multiple Issue Boards
](
#multiple-issue-boards
)
,
available only in
[
GitLab Enterprise Edition
](
https://about.gitlab.com/gitlab-ee/
)
,
each team (frontend and backend) can have their own boards to organize their flow among the
...
...
@@ -53,8 +63,16 @@ members of their teams. For that, we could have, therefore, three Issue Boards f
-
**Frontend**
, same as above, for the frontend team
-
**Deployment**
, for the entire process (backend > frontend > staging > production)
For a broader use-case, please check the blog post
[
GitLab Workflow, an Overview
](
https://about.gitlab.com/2016/10/25/gitlab-workflow-an-overview/#gitlab-workflow-use-case-scenario
)
.
### Boards for Milestones
From the use-cases above, let's assume that you have now created a milestone per release for
your app. You can create a milestone exclusive for each release, and associate it with a board.
Therefore, you'll have everything organized in a board per release.
### Focus Mode
When you are organizing your issues through an Issue Board and want to avoid distractions,
you can use the
[
Issue Board Forcus Mode
](
#focus-mode
)
.
## Issue Board terminology
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment