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 rank #2530

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

Originally created by @candlerb on GitHub (Apr 18, 2019).

Environment

  • Python version: 3.5.2
  • NetBox version: 2.5.10

Proposed Functionality

Currently, Netbox displays racks sorted left-to-right by name in the elevations view.

I propose adding a "rank" value, so that racks are sorted by rank. (Similar to: rank value for custom field choices). That is: you can set the rank to control the sequence of racks displayed.

Alternative: add a right-to-left ordering flag as an attribute of Rack Group. This is less general-purpose, but would be sufficient for my use case.

Use Case

In one particular site we have two rows of racks, but they are numbered in opposite directions when facing them:

  • S18 S17 S16 S15 S14
  • T14 T15 T16 T17 T18

Netbox shows the S row in the "wrong" order.

Workaround: I could rename the racks to 01-S18, 02-S17, 03-S16 etc.

Database Changes

Add "Rank" column to rack (or reverse ordering flag to Rack Group)

External Dependencies

None

Originally created by @candlerb on GitHub (Apr 18, 2019). ### Environment * Python version: 3.5.2 * NetBox version: 2.5.10 ### Proposed Functionality Currently, Netbox displays racks sorted left-to-right by name in the elevations view. I propose adding a "rank" value, so that racks are sorted by rank. (Similar to: rank value for custom field choices). That is: you can set the rank to control the sequence of racks displayed. Alternative: add a right-to-left ordering flag as an attribute of Rack Group. This is less general-purpose, but would be sufficient for my use case. ### Use Case In one particular site we have two rows of racks, but they are numbered in opposite directions when facing them: * S18 S17 S16 S15 S14 * T14 T15 T16 T17 T18 Netbox shows the S row in the "wrong" order. Workaround: I could rename the racks to 01-S18, 02-S17, 03-S16 etc. ### Database Changes Add "Rank" column to rack (or reverse ordering flag to Rack Group) ### External Dependencies None
adam added the status: duplicate label 2025-12-29 18:19:43 +01:00
adam closed this issue 2025-12-29 18:19:43 +01:00
adam commented 2025-12-29 18:19:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 19, 2019):

This should be covered by #114. I don't want to add anything now that we might have to undo down the road.

@jeremystretch commented on GitHub (Apr 19, 2019): This should be covered by #114. I don't want to add anything now that we might have to undo down the road.
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: duplicate
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#2530
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?