Ralf Peters Posted May 25, 2016 Share Posted May 25, 2016 Hi, don't know if this was intended but the "Request" search on the top of page is not searching for partial request numbers , partial search for all other categories seems to work. Thanks Ralf Link to comment Share on other sites More sharing options...
Guest Chaz Posted May 25, 2016 Share Posted May 25, 2016 Hi Ralf, you should be able to search for partial matches by using the wildcard character * For example, you could search for IN*91 and it would find all matches that started with IN AND ended with 91. The only restriction on this is that you cannot use a wildcard as the first character. In your screenshot it's found an exact match because there is an exact match, with the wildcard you can expect more results. Also, you may be interested to know that we have a keyboard shortcut for quickly opening up requests. If you hit CTRL+SHIFT+F you can enter a full request ID and it will take you straight there (if you have visibility of that request). Hope that all helps! Link to comment Share on other sites More sharing options...
Ralf Peters Posted May 25, 2016 Author Share Posted May 25, 2016 Thanks for the reply , i see your point , but why will it search any string for all the other categories or even in the request list ; not wildcards required here ? Link to comment Share on other sites More sharing options...
Guest Chaz Posted May 25, 2016 Share Posted May 25, 2016 Hi Ralf, thanks for the update, I will pick it up with the development team but it should be consistent and require wildcards when using the global search. Both the request and asset lists have very different approaches where it does a near match. I would say that the global search is designed for broader searches when it comes to requests and assets as they should both allow keywords like AND and OR as well as allowing for searching for exact phrases by using quotes. More info on this can be found here: https://wiki.hornbill.com/index.php/Workspaces#Advanced_Search As I said, will pick this up with development as there are some inconsistencies with searching for assets. Just so you know, we have some improvements to make around the search for requests which are part of the RFC CH00135338 (due in the next 90 days). Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now