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 Order / Rack Weights - currently theres no way to define which rack is to the left or right of a rack. #9347

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

Originally created by @ITJamie on GitHub (Mar 12, 2024).

NetBox version

v3.7.3

Feature type

Data model extension

Proposed functionality

add an "order/weight" field to rack objects.
use this weight field to decide the order of racks. currently, this happens by name of racks. which may not be correct and may be inverted if a row counts from a higher number on the left to lower numbers on the right.

Use case

places this info would be used:

  • elevation views - to sort order of racks
  • rack view - on the breadcrumb menu there are left and right arrows to step through the rack that is left or right of the current rack

Database changes

No response

External dependencies

No response

Originally created by @ITJamie on GitHub (Mar 12, 2024). ### NetBox version v3.7.3 ### Feature type Data model extension ### Proposed functionality add an "order/weight" field to rack objects. use this weight field to decide the order of racks. currently, this happens by name of racks. which may not be correct and may be inverted if a row counts from a higher number on the left to lower numbers on the right. ### Use case places this info would be used: - elevation views - to sort order of racks - rack view - on the breadcrumb menu there are left and right arrows to step through the rack that is left or right of the current rack ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:48:52 +01:00
adam closed this issue 2025-12-29 20:48:53 +01:00
adam commented 2025-12-29 20:48:53 +01:00
Author
Owner
Copy Link

@ravinald commented on GitHub (Mar 15, 2024):

When viewing racks you can do a reverse sort as a workaround. I was pondering this similar issue and how to make the sort order persistent. It probably makes sense to have this at the location object.

@ravinald commented on GitHub (Mar 15, 2024): When viewing racks you can do a reverse sort as a workaround. I was pondering this similar issue and how to make the sort order persistent. It probably makes sense to have this at the location object.
adam commented 2025-12-29 20:48:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 3, 2024):

use this weight field to decide the order of racks. currently, this happens by name of racks. which may not be correct and may be inverted if a row counts from a higher number on the left to lower numbers on the right.

NetBox itself does not attempt to track the physical location of racks relative to one another; there is no concept of "left" or "right." Further, a simple weight or ordering field would not be sufficient to convey this, as it does not address grouping or the orientation of individual racks. Introducing such a field would predictably beget additional feature requests for modeling more advanced layouts, which is currently our of scope for the core product.

Fortunately, there is a floorplan plugin which provides this functionality and more.

@jeremystretch commented on GitHub (Apr 3, 2024): > use this weight field to decide the order of racks. currently, this happens by name of racks. which may not be correct and may be inverted if a row counts from a higher number on the left to lower numbers on the right. NetBox itself does not attempt to track the physical location of racks relative to one another; there is no concept of "left" or "right." Further, a simple weight or ordering field would not be sufficient to convey this, as it does not address grouping or the orientation of individual racks. Introducing such a field would predictably beget additional feature requests for modeling more advanced layouts, which is currently our of scope for the core product. Fortunately, there is a [floorplan plugin](https://github.com/netbox-community/netbox-floorplan-plugin) which provides this functionality and more.
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: 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#9347
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?