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

Improve ways to insert devices in rack positions #6051

New Issue
Closed
opened 2025-12-29 19:36:04 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:36:04 +01:00
Owner
Copy Link

Originally created by @PieterL75 on GitHub (Feb 4, 2022).

NetBox version

v3.1.6

Feature type

Change to existing functionality

Proposed functionality

Adding a device to a rack can only be done through the 'Edit' form of a device.
This is simply, but not very inuitive and user friendly.

It would benefit to change the way this is done in the GUI.

  1. The edit form's Position field could get a 'Pick from rack' button. This would popup the rack and allow you to select the position visually.
  2. From the rack point of view
    When hovering over a free position, only 'Add Device' is shown. This links to the creation form of devices.
    It would benefit of this give you the option to link an existing device the, rather than creating a new one. I got the feeling that this rarely done from that view.
    Same goes for the 'Add non racked device' in this view.

Use case

This will help to visualize the racks when inserting devices into them.
Sometimes you know it has to go 'below that switch', without knowing the exact location

Database changes

None

External dependencies

None

Originally created by @PieterL75 on GitHub (Feb 4, 2022). ### NetBox version v3.1.6 ### Feature type Change to existing functionality ### Proposed functionality Adding a device to a rack can only be done through the 'Edit' form of a device. This is simply, but not very inuitive and user friendly. It would benefit to change the way this is done in the GUI. 1. The edit form's Position field could get a 'Pick from rack' button. This would popup the rack and allow you to select the position visually. 2. From the rack point of view When hovering over a free position, only 'Add Device' is shown. This links to the creation form of devices. It would benefit of this give you the option to link an existing device the, rather than creating a new one. I got the feeling that this rarely done from that view. Same goes for the 'Add non racked device' in this view. ### Use case This will help to visualize the racks when inserting devices into them. Sometimes you know it has to go 'below that switch', without knowing the exact location ### Database changes None ### External dependencies None
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:36:04 +01:00
adam closed this issue 2025-12-29 19:36:04 +01:00
adam commented 2025-12-29 19:36:05 +01:00
Author
Owner
Copy Link

@AnythingOverIP commented on GitHub (Feb 14, 2022):

For item # 2, I see 2 approaches:

  • instead of "Add Device", something like "new / assign" with different targets. Any non-racked devices at the site should be available for selection, not only the ones assigned to the rack but not racked.
  • Similar to what we have for assigning an IP address to an interface, when clicking on "Add Device", the page "Add a new device" could have a second tab to allow device assignation.

That same logic could be useful if implemented in the "Non-Racked Devices" table located under the rack view. Currently there's a "Add a Non-Racked Device" button that allow you to create a new device, but there's no direct option to assign a previously created device to the rack

@AnythingOverIP commented on GitHub (Feb 14, 2022): For item # 2, I see 2 approaches: * instead of "Add Device", something like "new / assign" with different targets. Any non-racked devices at the site should be available for selection, not only the ones assigned to the rack but not racked. * Similar to what we have for assigning an IP address to an interface, when clicking on "Add Device", the page "Add a new device" could have a second tab to allow device assignation. That same logic could be useful if implemented in the "Non-Racked Devices" table located under the rack view. Currently there's a "Add a Non-Racked Device" button that allow you to create a new device, but there's no direct option to assign a previously created device to the rack
adam commented 2025-12-29 19:36:05 +01:00
Author
Owner
Copy Link

@minitriga commented on GitHub (Mar 15, 2022):

I have worked on this and have been able to implement the Assign device after clicking through from non-racked devices and from the add device button on a rack. It will allow you to add racked and non-racked devices essentially swapping a device from one rack to another.

I think the Pick from rack button is a bit more difficult to implement as it would require many redirects or implementing a modal. It could be done but not by me I think as I don't know typescript all that well.

@minitriga commented on GitHub (Mar 15, 2022): I have worked on this and have been able to implement the Assign device after clicking through from non-racked devices and from the `add device` button on a rack. It will allow you to add racked and non-racked devices essentially swapping a device from one rack to another. I think the `Pick from rack` button is a bit more difficult to implement as it would require many redirects or implementing a modal. It could be done but not by me I think as I don't know typescript all that well.
adam commented 2025-12-29 19:36:06 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 15, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (May 15, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:36:06 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 14, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jun 14, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: needs owner 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#6051
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?