diff --git a/doc/bugs/make___39__find__39___clear__40__er__41___on_what_is_unlocked_.mdwn b/doc/bugs/make___39__find__39___clear__40__er__41___on_what_is_unlocked_.mdwn
index 201112fc5e..3624584ce9 100644
--- a/doc/bugs/make___39__find__39___clear__40__er__41___on_what_is_unlocked_.mdwn
+++ b/doc/bugs/make___39__find__39___clear__40__er__41___on_what_is_unlocked_.mdwn
@@ -61,3 +61,5 @@ no changes added to commit (use "git add" and/or "git commit -a")
 ```
 
 and I do not think it should report `124` as unlocked.  Or is there some `find` way to search only for "truly unlocked" files?
+
+> [[notabug|done]] --[[Joey]]
diff --git a/doc/bugs/make___39__find__39___clear__40__er__41___on_what_is_unlocked_/comment_1_b855c810464bb22bd76681d669313ae5._comment b/doc/bugs/make___39__find__39___clear__40__er__41___on_what_is_unlocked_/comment_1_b855c810464bb22bd76681d669313ae5._comment
new file mode 100644
index 0000000000..8ab89d2846
--- /dev/null
+++ b/doc/bugs/make___39__find__39___clear__40__er__41___on_what_is_unlocked_/comment_1_b855c810464bb22bd76681d669313ae5._comment
@@ -0,0 +1,19 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2022-02-21T19:16:13Z"
+ content="""
+The only difference between those two is that git-annex unlock stages the
+unlocking, while replacing the file with unlocked content does not stage
+it yet.
+
+Both files are unlocked in the working tree though. One is unlocked in
+the index, and the other one is not yet. But git-annex find examines the
+working tree.
+
+What you are looking for is a a way to have `git-annex find`
+ignore the working tree and find files that are unlocked in the index.
+That is doable:
+
+	git-annex find --branch=$(git write-tree) --unlocked
+"""]]