-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
globalsearch: search result view: ordering results by object_type not working #11383
Comments
I have a PR ready for this one. Edit: however, looks like ordering by Since the Some that haven't worked:
Any thoughts? |
…re reliable approach
Spent some time in the debugger looking through the result object list, but I couldn't find a single accessor that works across all search result object types. Any accessor I pass to I have the original issue resolved. @kkthxbye-code do you want me to move forward with that as a PR and leave object sorting as a separate bug, or do you have another idea on how to take care of object sorting too? |
@jeremystretch care to weigh in here? I can submit a PR for the original bugfix & open a new issue but wanted maintainer input first. |
Submitted my PR for original issue, opening new issue for object column sorting |
NetBox version
v3.4.2
Python version
3.10
Steps to Reproduce
goto: https://demo.netbox.dev/search/?q=100
press "Type" on the search results table header, results do not re-order
Expected Behavior
objects to be grouped together by object type when sorted by object_type. instead "field" seems to take precidence
Observed Behavior
Some of the same object types are split apart, eg on the demo site some of the device types are separated, also when you try and order in reverse the order does not seem to change.
In our internal instance we sometimes see devices intermingled with other objects.
sorting by "field" works as expected, sorting by "type" does not and seems to fallback to sorting by "field"
The text was updated successfully, but these errors were encountered: