starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-14 06:13:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add custom order for Racks #10435

New Issue
Open
opened 2025-12-29 21:31:27 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:31:27 +01:00
Owner
Copy Link

Originally created by @fknorn on GitHub (Nov 4, 2024).

NetBox version

v4.1.6

Feature type

Data model extension

Triage priority

N/A

Proposed functionality

Racks are arranged in a certain way in the physical world, and their names (rack IDs or whatever) not always correspond to that.

On the rack view page (/dcim/racks/<id>) there are handy "previous" and "next" buttons for rack navigation, but in about half of the cases they do not match the physical arrangement of racks in the row as when seen standing in front of the rack.

image

It would be handy to be able to - if so desired - specify a custom order by e.g. adding a number input based on which the ordering is carried out, specifically for these buttons.

Use case

More intuitive "left" / "right" navigation of racks.

Database changes

I'm no expert, but I guess the poor-person's solution would be to add an integer field based on which the sorting is then carried out.

External dependencies

None.

Originally created by @fknorn on GitHub (Nov 4, 2024). ### NetBox version v4.1.6 ### Feature type Data model extension ### Triage priority N/A ### Proposed functionality Racks are arranged in a certain way in the physical world, and their names (rack IDs or whatever) not always correspond to that. On the rack view page (`/dcim/racks/<id>`) there are handy "previous" and "next" buttons for rack navigation, but in about half of the cases they do not match the physical arrangement of racks in the row as when seen standing in front of the rack. ![image](https://github.com/user-attachments/assets/c46f31d7-eaec-4275-adfd-6ec8e00f49e6) It would be handy to be able to - if so desired - specify a custom order by e.g. adding a number input based on which the ordering is carried out, specifically for these buttons. ### Use case More intuitive "left" / "right" navigation of racks. ### Database changes I'm no expert, but I guess the poor-person's solution would be to add an integer field based on which the sorting is then carried out. ### External dependencies None.
adam added the type: featurecomplexity: mediumnetboxstatus: backlog labels 2025-12-29 21:31:27 +01:00
adam commented 2025-12-29 21:31:27 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Nov 5, 2024):

previously requested: https://github.com/netbox-community/netbox/issues/15412

@ITJamie commented on GitHub (Nov 5, 2024): previously requested: https://github.com/netbox-community/netbox/issues/15412
adam commented 2025-12-29 21:31:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 5, 2024):

Moving this to the backlog as introducing a new field for ordering would necessitate an API change.

@jeremystretch commented on GitHub (Nov 5, 2024): Moving this to the backlog as introducing a new field for ordering would necessitate an API change.
adam commented 2025-12-29 21:31:28 +01:00
Author
Owner
Copy Link

@doc-sheet commented on GitHub (Aug 10, 2025):

It looks like rack row model concept to organize neighbor racks in line similar to how devices organized with rack.

@doc-sheet commented on GitHub (Aug 10, 2025): It looks like rack row model concept to organize neighbor racks in line similar to how devices organized with rack.
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 complexity: medium netbox status: backlog 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#10435
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?