diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-04-22 21:09:52 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-04-22 21:09:52 +0300 |
| commit | db061f44328ca45f713eaf22d92aae8e76148fda (patch) | |
| tree | 56f1297f970cb41a13e27cae12f5e9665957c885 /doc/user/project/labels.md | |
| parent | 7a7345366550f509c03595e0dada7cbd0d73103d (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/project/labels.md')
| -rw-r--r-- | doc/user/project/labels.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/user/project/labels.md b/doc/user/project/labels.md index 9cf50d3aaed..618ef9cfc47 100644 --- a/doc/user/project/labels.md +++ b/doc/user/project/labels.md @@ -164,7 +164,7 @@ Suppose you have the labels `workflow::development`, `workflow::review`, and applied, and a developer wanted to advance the issue to `workflow::review`, they would simply apply that label, and the `workflow::development` label would automatically be removed. This behavior already exists when you move issues -across label lists in an [issue board](issue_board.md#creating-workflows), but +across label lists in an [issue board](issue_board.md#create-workflows), but now, team members who may not be working in an issue board directly would still be able to advance workflow states consistently in issues themselves. |