From c249e6cc3ae21e07ed0d6da76c9d244e08c7ddfc Mon Sep 17 00:00:00 2001 From: Cormac Foster Date: Fri, 5 Jun 2020 19:05:40 +0000 Subject: [PATCH] Remove "value" from the description of weight, as it confuses the goal of the Weight field (which, I believe, is supposed to be where we track time/complexity/story points, rather than business value). --- doc/user/project/issues/issue_weight.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/doc/user/project/issues/issue_weight.md b/doc/user/project/issues/issue_weight.md index 23c1520294ddf0..e052bbd20d5830 100644 --- a/doc/user/project/issues/issue_weight.md +++ b/doc/user/project/issues/issue_weight.md @@ -10,8 +10,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/76) in [GitLab Starter](https://about.gitlab.com/pricing/) 8.3. When you have a lot of issues, it can be hard to get an overview. -By adding a weight to each issue, you can get a better idea of how much time, -value or complexity a given issue has or will cost. +By adding a weight to each issue, you can get a better idea of a given issue's complexity or how much time it will cost. You can set the weight of an issue during its creation, by simply changing the value in the dropdown menu. You can set it to a non-negative integer -- GitLab