Wildcard search
N
Neon carrot Newt
All of our endpoints have an asset tag assigned to them, and that becomes their machine name. All tags are in the format of:
ABC-DE01234
Currently, we need to search DE01234 for the search to return results. We'd like to be able to just search the numbers as the letters DE can change.
I've tried adding * before the numbers but it made no difference. If there's already a wildcard operator out there please let me know :)
C
Coquelicot Seahorse
+1 for this feature. We really need this for the product to work for us!
S
Shy Reptile
I would be comfortable with all other feature development being put on hold in favor of better search! This is a fundamental aspect of the product that is deeply flawed. Stop everything else and improve this before ancillary features are developed/improved!
Kristen W.
Merged in a post:
Improve password searching
Y
Yarrow Squid
Add a more comprehensive / exact search when using the search bar in the passwords tab.
Searching for '365' came up empty but there are credentials that contain 'O365' and 'M365' in the name
Kristen W.
Merged in a post:
Basic Search Improvements
P
Pleased Shrimp
Wildcard search or an equivalent needs to be implemented as soon as possible. As far as I can tell, search has been a topic on this forum since January 2022, yet it doesn't appear the 100+ combined upvotes over these 2 years have affected the roadmap. This is a little disturbing, I hope to revive the movement.
It seems people have been relegated to requesting tags or similar to improve the search, but simply put, we need to be able to type in "365" and get all results like M365 and O365 and Office 365. Or if we use a strict naming scheme to keep things straight in documentation, say I'm looking for switches in a specific IDF and we name them ORG-IDF2-SW# for example, I should be able to search for "IDF2" and find all devices with that in the name. As of now, this is impossible, and makes it significantly harder to do something like creating an age report of said switches.
Please, Hudu, we're begging! This would significantly reduce the amount of time looking for simple stuff.
Kristen W.
Merged in a post:
Search Flaw
I
Increased Jaguar
After using your product for a few months, we noticed what we perceive to be a flaw in your Search Engine. When you search for items within Hudu, you must spell keywords correctly in sequential order to find the correct result.
Example:
In global search, I type in “365” expecting find any passwords and articles related to Office 365. However, our acronym for Office 365 is “O365”.
Unfortunately, because I didn’t put the character ‘O’ at the beginning of the string, I cannot get any results for Office 365. It took one of our technicians 4 attempts before he finally used the correct string that got him the results he wanted.
This is going to be a huge time waster for our technicians. We would like to know if there is a wildcard search feature or if you will be making search engine improvements to get us faster results with slightly inaccurate information.
-----NEW UPDATE-----
We have found that the search works perfectly when searching for Companies. In fact it even auto-query's the search and I do not have to type enter.
Kristen W.
Merged in a post:
Improve Search Capabilities
D
Distant Reptile
Search seems to be pretty limited right now. This is based on a few factors:
- Search is not wildcard on words. As an example, searching "365" will pull up assets name "Office 365" but not "M365."
- Search does not use the fields/contents of an asset. This limits the ability to search by IP address, KB article details, etc.
I think a robust solution to this would be adopting a service such as Algolia or Meilisearch.
R
Retired Pike
You should find it by selecting "exact" but yes, frustrating and they were allegedly rolling out a new search engine over 6mo ago.
To be honest, I would prefer exact search by default and fuzzy search only on selection because it doesn't rank or otherwise add weight to the obvious results. It also fails to match at certain character length thresholds because of the design.
Once you deploy naming standards, search by title shouldn't need much assistance from fuzzy logic.
R
Relieved Mastodon
Same here, not really useable this time.
N
Nutmeg Hedgehog
I agree that this is a flaw, we call it the partial search flaw. The same exact issue came up for an account, most techs put "Office 365" and we search 365, but for one client someone put Office365 or O365 instead, so nothing came up when searching passwords for 365. IT Glue worked this way, Hudu should fix it.
E
Endless Hummingbird
Doesn't this work as you described when you use the "Comprehensive" search?
Load More
→