Is this on vault.bitwarden.com? I pushed an update with some improvements.
For example: “customerXYZ beta” should now work since it will wildcard all words of the search query individually, instead of the entire query as a whole.
Can you refresh and try now?
Thanks for the suggestion, but unfortunately this doesn’t really help with the results. This seems to be an “OR” search operation now, since the results also include “beta” entries of other customers (not only customerXYZ).
No, we use a self-hosted instance - However, I just pre-/appended the asteriks to reproduce the new behaviour.
Is there a way to have a “AND” search operation like this rather than “OR” by default?
What is the subtitle field, please?
Thanks to @vincentsalucci for the help on this one 
Subtitles are generated off existing data, per item type:
Thanks for getting back at me so fast!
“Secure Note -> null”
Does that mean no information from secure notes is used?
No problem!
Re: secure notes, it just means there is no subtitle property, but the note is searched.
Got it. You guys rock!
Please kindly consider the following.
You can see below I have created a Login. I like to add tags in the Notes section to assist in finding the Login. Notice the commas immediately after tag1 & tag2, but no comma after tag3.
You can see below, if I type ‘tag1’ or ‘tag2’ into the Search textbox, the Login is not found. This is due to the comma at the end of the tag.
You can see below, if I type ‘tag3’ into the Search textbox, the Login is found. This is due to no comma or other symbol at the end of the tag.
It would be great if this was fixed. I can work around it, by not putting symbols directly after words, however this is not the normal way people type sentences or lists.
Here are a couple related, existing Feature Requests:
Its been a month now I moved from Lastpass to Bitwarden. I really love Bitwarden.
Is there already a feature request out there for below?
Suppose I have hundreds of Login and Secure Notes. In one of the Secure Notes I have a sentence ‘eucalyptus oil has been used to relieve coughing’. Now if I search using partial text ‘eucal’, it won’t search the exact Secure Note. But if I search using full string ‘eucalyptus’ it can search it.
It would be better to have ability to search using partial text also.
Have you tried this?
@desairb
The discussion in feature request Search within and inside all notes is mostly on partial search.
There is an older feature request Change Default Search to Wildcard Rather Than Exact Match which may also be related.
The LunrJS search syntax that @Peter_H linked is the currently supported option.
Example:
@Peter_H, thanks, this is great. This works and helpful.
A post was merged into an existing topic: Search: Combine search terms rathen than add them up
Searching by partial keyword doesn’t return results, the entire word must be typed. Moving from another password manager I got used to it being enough to only know part of the keyword to get results.
The same functionality missing in the Chromium extension (2024.10.1) as well as the Web Vault.
Leading and trailing wildcards are automatically applied when searching for terms in the item Name or URI fields. Therefore, you only need to enter pers or even rson to pull up the Personal finance tracking item; likewise, searching for goo, oog, or le.co would pull up any item that contains a URI in the google.com domain.
In contrast, for free text contained in the Notes field or in custom text fields, wildcards must be explicitly added to the search term, unless you are searching for the full word (or, more specifically, a token, which is a string of characters separated form other text by whitespace or hyphens).
There is a history of user requests to switch the search engine to one that is more intuitive, and I have now merged your post and some of the existing feature requests on the same topic.
Until such time that improvements are made to Bitwarden’s search function, these are the three workarounds I would suggest for you:
Search using explicit wildcards: e.g., search for budg* instead of budge.
If you are entering a list of keywords into a vault item to assist with searching, then store the keywords in a URI field instead of in a custom field or in the Notes. You may also want to click the 
icon for that URI, and set the match detection method to “Never”. Storing the keywords in a URI field will allow them to be found using implicit wildcards (e.g., searching for budg will find the keyword budget).
If you only have a limited number of keywords, and you do not like the URI field trick described above, then consider storing partial forms of the keywords. For example, instead of just budget and spending, make your keyword list include bu bud budg budge budget as well as sp spe spen spend spendi spendin spending.
Also, if you do continue to store keywords in the Notes section or in custom fields, then make sure that each keyword is separated from the others using only whitespace (or hyphens). For example, if you separate the keywords using punctuation (other than a hyphen), then you may have trouble searching for them. For example, if your keywords are stored as Budget, Money, Spending, then you will not be able to find this item by searching for budget unless you also include the trailing comma (budget,) or a trailing wildcard (budget*).
Noted and confirmed. Thank you, @grb
Although it would be nice to have implied wildcards when searching for anything, this is certainly better nothing.
This is not a universally held preference. In large part because it tends to result in lots of noise when searching for something like “metric” in a document full of “biometrics”.
@DenBesten
Good point. Thank you for showing me that perspective.
