starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Ordering of global search results #959

New Issue
Closed
opened 2025-12-29 16:27:16 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:27:16 +01:00
Owner
Copy Link

Originally created by @candlerb on GitHub (May 17, 2017).

Issue type:

Feature request

This is a very minor suggestion!

The new global search facility (#159) is superb. However at the moment if you search for an individual IP address you get the results in the following order:

  • Prefixes
  • Aggregates
  • IP Addresses

I think it would be more user-friendly to display from more specific match to less specific, which would be:

  • IP Addresses
  • Prefixes
  • Aggregates

Additional suggestion: make the drop-down menu of object types arranged in the same order as the search results are displayed, for consistency.

Originally created by @candlerb on GitHub (May 17, 2017). ### Issue type: Feature request This is a very minor suggestion! The new global search facility (#159) is superb. However at the moment if you search for an individual IP address you get the results in the following order: * Prefixes * Aggregates * IP Addresses I think it would be more user-friendly to display from more specific match to less specific, which would be: * IP Addresses * Prefixes * Aggregates Additional suggestion: make the drop-down menu of object types arranged in the same order as the search results are displayed, for consistency.
adam added the type: bug label 2025-12-29 16:27:16 +01:00
adam closed this issue 2025-12-29 16:27:16 +01:00
adam commented 2025-12-29 16:27:16 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (May 17, 2017):

A related display issue:

Searching for device via global search doesn't show its IP address in the results listing, but searching via devices page does.

Results from global search:

image

Results from search under /dcim/devices/

image

It would be nice if the global search results had the same columns as the specific searches.

@candlerb commented on GitHub (May 17, 2017): A related display issue: Searching for device via global search doesn't show its IP address in the results listing, but searching via devices page does. Results from global search: ![image](https://cloud.githubusercontent.com/assets/44789/26146908/b474bcc6-3ae9-11e7-9806-574f4c466aec.png) Results from search under `/dcim/devices/` ![image](https://cloud.githubusercontent.com/assets/44789/26146934/cbe48a4e-3ae9-11e7-822e-9c87099e9bc4.png) It would be nice if the global search results had the same columns as the specific searches.
adam commented 2025-12-29 16:27:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 17, 2017):

The order of objects returned from a global search is currently not enforced. I'll change this to an OrderedDict to ensure consistency.

Searching for device via global search doesn't show its IP address in the results listing, but searching via devices page does.

We avoid pulling in too many related objects due to the breadth of the current global search implementation. For example, we also don't calculate rack utilization.

@jeremystretch commented on GitHub (May 17, 2017): The order of objects returned from a global search is currently not enforced. I'll change this to an OrderedDict to ensure consistency. > Searching for device via global search doesn't show its IP address in the results listing, but searching via devices page does. We avoid pulling in too many related objects due to the breadth of the current global search implementation. For example, we also don't calculate rack utilization.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#959
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?