Commit 3a0e9df6 authored by Marcia Ramos's avatar Marcia Ramos

Axil's review

parent 976e738f
...@@ -28,8 +28,8 @@ empowered with the ability to create multiple boards per project. ...@@ -28,8 +28,8 @@ empowered with the ability to create multiple boards per project.
## Use-cases ## Use-cases
There are numerous use-cases for the use of Issue Boards, we will just There are numerous use-cases for Issue Boards, we will just
exemplify with a couple situations, but the possibilities go where our creativity goes. exemplify with a couple situations.
For a broader use-case, please check the blog post 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). [GitLab Workflow, an Overview](https://about.gitlab.com/2016/10/25/gitlab-workflow-an-overview/#gitlab-workflow-use-case-scenario).
...@@ -37,7 +37,7 @@ For a broader use-case, please check the blog post ...@@ -37,7 +37,7 @@ For a broader use-case, please check the blog post
### Single Board ### Single Board
GitLab Workflow allows you to discuss proposals in issues, categorize them GitLab Workflow allows you to discuss proposals in issues, categorize them
with labels, and and from there organize and prioritize them with Issue Boards. with labels, and from there organize and prioritize them with Issue Boards.
- For example, let's consider this simplified development workflow: - For example, let's consider this simplified development workflow:
you have a repository hosting your app's codebase you have a repository hosting your app's codebase
...@@ -57,7 +57,7 @@ beginning of the dev lifecycle until deployed to production ...@@ -57,7 +57,7 @@ beginning of the dev lifecycle until deployed to production
To enhance the workflow exemplified above, with [Multiple Issue Boards](#multiple-issue-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/), 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 each team (frontend and backend) can have their own boards to organize their flow among the
members of their teams. For that, we could have, therefore, three Issue Boards for this case: members of their teams. We could have, therefore, three Issue Boards for this case:
- **Backend**, for the backend team and their own labels and workflow - **Backend**, for the backend team and their own labels and workflow
- **Frontend**, same as above, for the frontend team - **Frontend**, same as above, for the frontend team
...@@ -235,7 +235,7 @@ existing one. ...@@ -235,7 +235,7 @@ existing one.
![Multiple Issue Boards](img/issue_boards_multiple.png) ![Multiple Issue Boards](img/issue_boards_multiple.png)
### Board with a Milestone ### Board with a milestone
> Introduced in [GitLab Enterprise Edition][ee] 9.0. > Introduced in [GitLab Enterprise Edition][ee] 9.0.
......
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