summaryrefslogtreecommitdiff
path: root/doc/user/project
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2021-06-14 21:10:22 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2021-06-14 21:10:22 +0000
commit5b829393a732143e31e2f9a62b6ca2cfb7ebb147 (patch)
tree85260ce9fd49ea62df0cea5b750f8c0db1b5a082 /doc/user/project
parentf69bc1dab50e86440bb4ffdc507ca5efd94bf459 (diff)
downloadgitlab-ce-5b829393a732143e31e2f9a62b6ca2cfb7ebb147.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/project')
-rw-r--r--doc/user/project/issues/design_management.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/user/project/issues/design_management.md b/doc/user/project/issues/design_management.md
index 8b67c7e03ce..8c42a27b471 100644
--- a/doc/user/project/issues/design_management.md
+++ b/doc/user/project/issues/design_management.md
@@ -219,6 +219,9 @@ There are two ways to resolve/unresolve a Design thread:
![Resolve checkbox](img/resolve_design-discussion_checkbox_v13_1.png)
+Resolving a discussion thread will also mark any pending to-do related to notes
+inside the thread as done. This is applicable only for to-dos owned by the user triggering the action.
+
Note that your resolved comment pins disappear from the Design to free up space for new discussions.
However, if you need to revisit or find a resolved discussion, all of your resolved threads are
available in the **Resolved Comment** area at the bottom of the right sidebar.