summaryrefslogtreecommitdiff
path: root/doc/user/project
diff options
context:
space:
mode:
authorGeorge Tsiolis <tsiolis.g@gmail.com>2018-07-24 12:53:05 +0300
committerGeorge Tsiolis <tsiolis.g@gmail.com>2018-07-24 12:53:05 +0300
commitac3f92391c1edce9d3f8996f68013b49e032c9d1 (patch)
treeaf0d03e1d5f18c88028a9de1dccfe87a25671e4d /doc/user/project
parentd4e9cd9de49a9f2b90ab76c5dc63d1515f9fdd69 (diff)
downloadgitlab-ce-ac3f92391c1edce9d3f8996f68013b49e032c9d1.tar.gz
Update improve issue boards links to docs [ci skip]
Diffstat (limited to 'doc/user/project')
-rw-r--r--doc/user/project/issue_board.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/user/project/issue_board.md b/doc/user/project/issue_board.md
index 860edb8e6f7..6dfdbe6c0d5 100644
--- a/doc/user/project/issue_board.md
+++ b/doc/user/project/issue_board.md
@@ -27,7 +27,7 @@ You create issues, host code, perform reviews, build, test,
and deploy from one single platform. Issue Boards help you to visualize
and manage the entire process _in_ GitLab.
-With [Multiple Issue Boards](#multiple-issue-boards), available
+With [Multiple Issue Boards](#use-cases-for-multiple-issue-boards), available
only in [GitLab Enterprise Edition](#features-per-tier),
you go even further, as you can not only keep yourself and your project
organized from a broader perspective with one Issue Board per project,
@@ -75,7 +75,7 @@ each team can have their own board to organize their workflow individually.
#### Scrum team
-With multiple Issue Boards, each team has one board. Now you can move issues through each
+With Multiple Issue Boards, each team has one board. Now you can move issues through each
part of the process. For instance: **To Do**, **Doing**, and **Done**.
#### Organization of topics