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

Alphabetize objects in each subsection under global search #5464

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

Originally created by @slash-proc on GitHub (Oct 5, 2021).

NetBox version

v3.0.5

Feature type

Change to existing functionality

Proposed functionality

Alphabetizing objects in each subsection under "All Objects" global search.

Use case

When trying to specify a specific object in the "All Objects" search field at the top of a given netbox page, the objects under the categories Circuits, DCIM, IPAM, Tenancy and Virtualization are not sorted alphabetically. This makes it difficult to quickly pick the appropriate object when a given subsection has many objects in it (for instance under DCIM)

image

Database changes

No response

External dependencies

No response

Originally created by @slash-proc on GitHub (Oct 5, 2021). ### NetBox version v3.0.5 ### Feature type Change to existing functionality ### Proposed functionality Alphabetizing objects in each subsection under "All Objects" global search. ### Use case When trying to specify a specific object in the "All Objects" search field at the top of a given netbox page, the objects under the categories Circuits, DCIM, IPAM, Tenancy and Virtualization are not sorted alphabetically. This makes it difficult to quickly pick the appropriate object when a given subsection has many objects in it (for instance under DCIM) ![image](https://user-images.githubusercontent.com/33379854/135992807-42ac11e8-4d49-47d8-9bb8-1dede865da97.png) ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: under review labels 2025-12-29 19:28:21 +01:00
adam closed this issue 2025-12-29 19:28:21 +01:00
adam commented 2025-12-29 19:28:22 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 5, 2021):

I think personally I prefer them in the current order, which closely follows how they appear in the navigation menu, but open to other opinions.

@jeremystretch commented on GitHub (Oct 5, 2021): I think personally I prefer them in the current order, which closely follows how they appear in the navigation menu, but open to other opinions.
adam commented 2025-12-29 19:28:22 +01:00
Author
Owner
Copy Link

@slash-proc commented on GitHub (Oct 6, 2021):

Maybe I still just need to get used to 3.x... I concede that alphabetization is the wrong way to go about things however the DCIM section is cluttered and I found myself repeatedly scrolling up and down to find "Devices" in particular.

I have a couple ideas but nothing concrete so I'll just go ahead and close this issue.

If I can come up with something better, I'll open a new issue with a properly thought-out suggestion.

@slash-proc commented on GitHub (Oct 6, 2021): Maybe I still just need to get used to 3.x... I concede that alphabetization is the wrong way to go about things however the DCIM section is cluttered and I found myself repeatedly scrolling up and down to find "Devices" in particular. I have a couple ideas but nothing concrete so I'll just go ahead and close this issue. If I can come up with something better, I'll open a new issue with a properly thought-out suggestion.
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 status: under review type: feature
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#5464
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?