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

Sort Tenants Alphabetically in API and Drop Downs #5198

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

Originally created by @bellwood on GitHub (Aug 18, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v2.11.11

Feature type

Change to existing functionality

Proposed functionality

Today, Tenants are sorted by their associated Tenant Group.

In the Tenants view, in the GUI, this makes sense as visually you can see the associated group information.

In API responses and GUI drop downs this is less than desirable as the sorted results are unexpected and arbitrary.

One would expect the results to be sorted alphabetically or naturally.

Use case

From an UI/UX perspective, all drop downs should be sorted similarly to avoid confusion and aid in user input.

From an API perspective, having the results sorted by tenant groups, is arbitrary.

Database changes

None

External dependencies

None

Originally created by @bellwood on GitHub (Aug 18, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v2.11.11 ### Feature type Change to existing functionality ### Proposed functionality Today, Tenants are sorted by their associated Tenant Group. In the Tenants view, in the GUI, this makes sense as visually you can see the associated group information. In API responses and GUI drop downs this is less than desirable as the sorted results are unexpected and arbitrary. One would expect the results to be sorted alphabetically or naturally. ### Use case From an UI/UX perspective, all drop downs should be sorted similarly to avoid confusion and aid in user input. From an API perspective, having the results sorted by tenant groups, is arbitrary. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 19:25:21 +01:00
adam closed this issue 2025-12-29 19:25:21 +01:00
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: accepted 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#5198
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?