diff options
author | Marcia Ramos <virtua.creative@gmail.com> | 2017-06-28 20:51:59 -0300 |
---|---|---|
committer | Marcia Ramos <virtua.creative@gmail.com> | 2017-06-28 20:51:59 -0300 |
commit | 07b9f48fb3b4eaf7c3c5ca83109fa758a7c23b13 (patch) | |
tree | 84d3c70229ea02c675a6362ede9eabe0c0398a0e | |
parent | 93646acc1c63baa03c2406d09e3a11036e520d6f (diff) | |
download | gitlab-ce-07b9f48fb3b4eaf7c3c5ca83109fa758a7c23b13.tar.gz |
remove multiple IB part
-rw-r--r-- | doc/user/project/issue_board.md | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/doc/user/project/issue_board.md b/doc/user/project/issue_board.md index 89819189864..ebd7b72d404 100644 --- a/doc/user/project/issue_board.md +++ b/doc/user/project/issue_board.md @@ -22,10 +22,6 @@ With the Issue Board you can have a different view of your issues while also maintaining the same filtering and sorting abilities you see across the issue tracker. -With [Multiple Issue Boards](#multiple-issue-boards), available only in [GitLab -Enterprise Edition](https://about.gitlab.com/gitlab-ee/), your workflow gets -empowered with the ability to create multiple boards per project. - ## Use-cases GitLab Workflow allows you to discuss proposals in issues, categorize them @@ -44,15 +40,6 @@ 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 -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 -members of their teams. For that, we could have, therefore, three Issue Boards for this case: - - - **Backend**, for the backend team and their own labels and workflow - - **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). |