summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSean McGivern <sean@gitlab.com>2019-04-24 11:00:23 +0100
committerSean McGivern <sean@gitlab.com>2019-04-24 11:00:23 +0100
commit7b0ee6464de2b40f72885a3f0a00d89dbc6db2cd (patch)
tree34b2b12b082182f1a293cc73b561943ce6f13ace
parent272071219e5b8261352b4b98431a78d51a93ccda (diff)
downloadgitlab-ce-7b0ee6464de2b40f72885a3f0a00d89dbc6db2cd.tar.gz
Clarify that reporters can manage boards
The original issue didn't specify this, but the code always allowed reporters to do everything here. I think that's correct because 1. Developer permissions normally refer to code, and boards are to do with issues. 2. Reporters can manage epics, as well as labels on issues, which are in a similar space.
-rw-r--r--doc/user/project/issue_board.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/user/project/issue_board.md b/doc/user/project/issue_board.md
index ad47b848bea..31020de5208 100644
--- a/doc/user/project/issue_board.md
+++ b/doc/user/project/issue_board.md
@@ -151,7 +151,7 @@ Create lists for each of your team members and quickly drag-and-drop issues onto
## Permissions
-[Developers and up](../permissions.md) can use all the functionality of the
+[Reporters and up](../permissions.md) can use all the functionality of the
Issue Board, that is, create or delete lists and drag issues from one list to another.
## GitLab Enterprise features for Issue Boards