Inconsistent search functionality

Ask the Community Password Manager
, , ,
1

So I thought this would be simple! I want to search for an item, but there are multiple versions in different collections. I therefore select the collection I want and try to search there but no results returned.

I logged a case with support, including a screen recording.

They then replied asking to confirm if I was searching for an item in a nested collection. I confirmed I was (collection Customers, sub-collection per customer) - they said “The behavior you are experiencing currently is the intended behavior in Bitwarden, as searching within a nested collection is currently not supported in Bitwarden.“

However I knew it had worked OK before for me!

So I then tried again - definitely the same behaviour seen, but then realised this was in Microsoft Edge - I switched over to Google Chrome (both have the Bitwarden extension installed and both are on the latest version - 2026.2.0, both synced to the same vault) - and search works there exactly as expected, either across the whole vault or within a collection or nested collection!

Is anyone else noticing this inconsistent behaviour between Edge/Chrome? Surely being able to search within a collection or nested collection must be expected to work?

image
image583×584 15.5 KB

2

This may have been a misunderstanding on their part (or yours). As far as I know, the only limitation is that if you search in a “parent” collection, then the “child” (nested) collections would not be included in the search results (and vice versa: if you search in a “child” collection, then any matching items stored in the “parent” collection will not show up in the search results).

I haven’t tested this in Edge, so it is possible that a regression has occurred.

3

Thanks for the reply. They specifically asked if I was searching for a vault item or collection and I confirmed the former. I agree it’s fair to not search within nested collections but rather surprised it didn’t filter as expected. Have rebooted the machine and is now working in Edge so looks like it’s a bug after all but an intermittent one, always more frustrating!