summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarcia Ramos <marcia@gitlab.com>2019-09-11 10:27:11 +0000
committerMarcia Ramos <marcia@gitlab.com>2019-09-11 10:27:11 +0000
commit31ff8ceff10d792be0c2166fed7511060f2a19fa (patch)
treed59b45df51bfdc14e4c355c4fe960b905a6d57fa
parent1ba9f029e89e99a245a201c21a98f4f79dc7b302 (diff)
parente877d758e9182e6178ff8766a082790abee6508f (diff)
downloadgitlab-ce-31ff8ceff10d792be0c2166fed7511060f2a19fa.tar.gz
Merge branch 'docs-62122-non-member-resolve-unresolve-discussion' into 'master'
Update docs for non member unresolving resolved thread See merge request gitlab-org/gitlab-ce!32375
-rw-r--r--doc/user/discussions/index.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/user/discussions/index.md b/doc/user/discussions/index.md
index 6b748981106..a198d83fac5 100644
--- a/doc/user/discussions/index.md
+++ b/doc/user/discussions/index.md
@@ -36,6 +36,9 @@ Thread resolution helps keep track of progress during planning or code review.
Every standard comment or thread in merge requests, commits, commit diffs, and
snippets is initially displayed as unresolved. They can then be individually resolved by anyone
with at least Developer access to the project or by the author of the change being reviewed.
+If the thread has been resolved and a non-member unresolves their own response,
+this will also unresolve the discussion thread.
+If the non-member then resolves this same response, this will resolve the discussion thread.
The need to resolve all standard comments or threads prevents you from forgetting
to address feedback and lets you hide threads that are no longer relevant.