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

Assign existing device to rack from rack layout window #1504

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

Originally created by @tbasten on GitHub (Jan 21, 2018).

[x] Feature request
[ ] Bug report
[ ] Documentation
Environment

Python version: 3.5.2
NetBox version: 2.2.8

Description

Would love to be able to assign existing devices to a rack slot when you click Add Device from the rack layout Window.

I see it being similar to how you can search for an IP address when assigning an IP to a management interface.

Originally created by @tbasten on GitHub (Jan 21, 2018). [x] Feature request [ ] Bug report [ ] Documentation Environment Python version: 3.5.2 NetBox version: 2.2.8 Description Would love to be able to assign existing devices to a rack slot when you click Add Device from the rack layout Window. I see it being similar to how you can search for an IP address when assigning an IP to a management interface.
adam added the type: feature label 2025-12-29 16:32:32 +01:00
adam closed this issue 2025-12-29 16:32:32 +01:00
adam commented 2025-12-29 16:32:32 +01:00
Author
Owner
Copy Link

@tb-killa commented on GitHub (Jan 10, 2019):

Hi @lampwins maybe this is something for your "select2" implementation ?

For this we should add a simple "dropdown" Menu on the Button Layer "add device" who open two Subs
or something equal:

  • Add New Device
  • Add existing Device

If existing Device is selected we could use "select2" work and bring in search bar who you type the name of your device like a live search and select.

Does we could search for Devices who are not assigned to any Rack ? This should be the Param for the query.

This would be the simplest solution i think.

@tb-killa commented on GitHub (Jan 10, 2019): Hi @lampwins maybe this is something for your "select2" implementation ? For this we should add a simple "dropdown" Menu on the Button Layer "add device" who open two Subs or something equal: - Add New Device - Add existing Device If existing Device is selected we could use "select2" work and bring in search bar who you type the name of your device like a live search and select. Does we could search for Devices who are not assigned to any Rack ? This should be the Param for the query. This would be the simplest solution i think.
adam commented 2025-12-29 16:32:32 +01:00
Author
Owner
Copy Link

@PeepOks commented on GitHub (May 13, 2019):

It think better "add-device" to rack can be done same way like "Add IP Address" to interface is done.
"Add device" view should include "add existing device" tab. In this view only devices, that are in same "Site" as rack is, should be listed.

After new or existing device is added to rack, there should be redirect to rack view where we started. I think "return_url" variable can be used for that.

@PeepOks commented on GitHub (May 13, 2019): It think better "add-device" to rack can be done same way like "Add IP Address" to interface is done. "Add device" view should include "add existing device" tab. In this view only devices, that are in same "Site" as rack is, should be listed. After new or existing device is added to rack, there should be redirect to rack view where we started. I think "return_url" variable can be used for that.
adam commented 2025-12-29 16:32:32 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Feb 21, 2020):

As discussed in PR #4190 , we should consider again this function.

@kobayashi commented on GitHub (Feb 21, 2020): As discussed in PR #4190 , we should consider again this function.
adam commented 2025-12-29 16:32:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 16, 2020):

I'm closing this feature as we've found that the development overhead it requires outweighs the minor convenience it provides.

@jeremystretch commented on GitHub (Mar 16, 2020): I'm closing this feature as we've found that the development overhead it requires outweighs the minor convenience it provides.
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#1504
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?