Improve search in the Knowledge Base module
The current search in the Knowledge Base seems to only do an exact match and only a single match. For example if you search MOVE MOUSE it would return the match "Move Mouse to select text" but if you search MOUSE MOVE it would not return this. It makes searching knowledge base very limited because you can do multiple keyword searches as it stands today.
Thank you for your UserVoice suggestion. This request has aged without many votes, so we are going to close it and free up your votes. If you still feel that it should be reconsidered, please feel create a new UserVoice request. Thank you again for your contribution!
Jesse M commented
This is a significant deficit in this product. Modern search capabilities are expected, and rightly so. The absence of this feature makes searching for old solutions difficult at best. Even a wildcard OR, the ability to separate terms, or support for boolean would be a major improvement.
Scott Mattingly commented
We have been asking for usable search for years, to the point we have put it in our requirements and as we are selecting a new solution to upgrade, we can no longer consider the K1000 because they have just not put in any effort to allow usable search. It's disappointing because it hit the mark on just about everything else.
Jason Clifford commented
Search is far too common a feature in this day and age and is a part of nearly every computer, web page, and app, to have it function in such a non-standard fashion. Users are accustomed to the de facto standard way that search works in most places, so KB search should at least work similarly. Furthermore, even if you know that the search feature will match an exact phrase and only an exact phrase (as I do), that is far too restrictive to be very useful. I sometimes even have a hard time finding a KB article to send to a user when I was the one who wrote it.
John Williams commented
Searching needs to be improved by searching by word instead of searching for the entire search string. It doesn't have to be on par with Google, but the current search mechanism prohibits us from truly utilizing this module.