-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set default globalsearch lookuptype #17138
Comments
This seems like it would result in a lot of confusion and frustration. Initializing the form with a predictable value every time is more user-friendly. |
I don't see how this can cause confusion. The setting should be retained per user. Each user than has the experience he choose. |
|
That is not the behavior I propose. (But indeed an optional behavior, so let's ignore that one) The FR is too allow the user to set the default lookup type for him. This will give him a consistent experience. |
It's the same problem though, really. Once a default has been set for some temporary purpose, it will likely be forgotten. |
I can't imagine one sets the default and forget about it. It's the main used feature of NetBox. All I do is search, change the lookup, search again... Maybe get some more voices and poll on slack? |
What do you think of the following compromise?
I think this limits user confusion to the bare minimum as you need to click on your own bookmark and then ignore what is selected in the form. |
I completely agree with the concerns raised in this issue. The current default setting for global search in NetBox is "partial match," which often leads to less relevant results, especially when searching for exact site names. Having to manually switch the lookup type to "exact match" for precise results is indeed cumbersome. Implementing a feature that allows users to set their preferred default search behavior, or at least remembers the last used lookup type, would significantly enhance the user experience. This adjustment would streamline workflows by reducing repetitive actions and ensuring that search results align more closely with user expectations. This enhancement aligns with previous discussions and issues where the need for more intuitive and user-friendly search functionalities has been highlighted. |
I see both sides of that discussion. It would be nice to set the default search behavior for myself. On the other side i understand that for most standard users this could be confusing. My approach would be: If we can not have this feature requested maybe it is possible to change the partial match behavior to set the match which is nearest to the query (often the exact match) is shown on first position. (sorting by relevance) |
NetBox version
v4.0.8
Feature type
Data model extension
Proposed functionality
the default globalsearch lookuptype is set to partial match.
a user should be able to select its own preference for the default value.
another option, is that the last used lookuptype is saved for the user.
Use case
as a user I prefer to have the 'regex' as a default search option. currently, I have to search, change the lookuptype, search again.
Database changes
An extra selector field is required on the user profile.
External dependencies
No response
The text was updated successfully, but these errors were encountered: