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

Rack Elevation Sorting Enhancement #6629

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

Originally created by @NavyWings on GitHub (Jul 5, 2022).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.2.2

Feature type

Change to existing functionality

Proposed functionality

Would be a helpful feature if we were able to sort the rack elevation by rack facility ID.

Currently, the rack elevation view sorts only on rack name. It can be sorted in "normal" (numerically ascending) or "reversed" (numerically descending.)"

Use case

Rack naming conventions are dependent on organization, not all entities name or number racks in a contiguous linear fashion from left to right. In our case, our center racks are numbered racks one and two and numbering increases as you move further from the center racks. It would be a helpful feature to see the rack elevation ordered by facility ID from left to right while retaining a custom rack naming at the top.

Database changes

Likely none, but unknown.

External dependencies

None

Originally created by @NavyWings on GitHub (Jul 5, 2022). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.2.2 ### Feature type Change to existing functionality ### Proposed functionality Would be a helpful feature if we were able to sort the rack elevation by rack facility ID. Currently, the rack elevation view sorts only on rack name. It can be sorted in "normal" (numerically ascending) or "reversed" (numerically descending.)" ### Use case Rack naming conventions are dependent on organization, not all entities name or number racks in a contiguous linear fashion from left to right. In our case, our center racks are numbered racks one and two and numbering increases as you move further from the center racks. It would be a helpful feature to see the rack elevation ordered by facility ID from left to right while retaining a custom rack naming at the top. ### Database changes Likely none, but unknown. ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 19:43:18 +01:00
adam closed this issue 2025-12-29 19:43:18 +01:00
adam commented 2025-12-29 19:43:18 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Aug 25, 2022):

@jeremystretch The current sort is a button-toggle, which wouldn't work for adding any new sorting. If we add this I see two potential solutions:

  1. Add a "Sort By" dropdown in-place of the buttons, with options "Name (A-Z)", "Name (Z-A)", "Facility ID (A-Z)", "Facility ID (Z-A)" could also use (Ascending) / (Descending) instead of (A-Z).
  2. Move the button below the tabs and have a "Sort By: " and then the dropdown showing the current sorting. (see screenshot)

I looked around and all the other sorting is done by column headers, so this looks like a sort of one-off UI.

sortby

@arthanson commented on GitHub (Aug 25, 2022): @jeremystretch The current sort is a button-toggle, which wouldn't work for adding any new sorting. If we add this I see two potential solutions: 1. Add a "Sort By" dropdown in-place of the buttons, with options "Name (A-Z)", "Name (Z-A)", "Facility ID (A-Z)", "Facility ID (Z-A)" could also use (Ascending) / (Descending) instead of (A-Z). 2. Move the button below the tabs and have a "Sort By: " and then the dropdown showing the current sorting. (see screenshot) I looked around and all the other sorting is done by column headers, so this looks like a sort of one-off UI. ![sortby](https://user-images.githubusercontent.com/99642/186536188-47d35b2e-9d90-4bd4-b051-aa99741f02f1.png)
adam commented 2025-12-29 19:43:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 26, 2022):

I think a dropdown with all four combinations makes sense. A-Z and Z-A is fine.

@jeremystretch commented on GitHub (Aug 26, 2022): I think a dropdown with all four combinations makes sense. A-Z and Z-A is fine.
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#6629
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?