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

Child Devices Creation / Assignation in web UI #1335

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

Originally created by @AnythingOverIP on GitHub (Oct 19, 2017).

Issue type

[ X ] Feature request

Environment

  • Python version: 3.5.4
  • NetBox version: 2.2.1

Description

From the "Add a new device" page, when adding a device with a type declared as a Child device, it would be useful to have the option to assign it directly to a device with an empty slot. (i.e.: in the "location section" of the page, the rack face & position could probably switched to "a field showing the available devices with a free slot".

Also, when looking at a device page ( /dcim/devices/xxxx/ ), when clicking on the green plus sign of a vacant slot to "install a device", it currently shows already created devices. Adding a "Create a new child device and assign to current parent" would be a real time saver.

When we create a server, our current data model requires us to separate the management port (i.e. iDrac, ILOM, RMM, etc.) from the server but we attach it to the main server as a separate device. The reason for this is that the management port has it's own device name & OS and is separate from the main box.

We have to create the server as a device, than create a management device, then go back to the server and assign it.

Originally created by @AnythingOverIP on GitHub (Oct 19, 2017). ### Issue type [ X ] Feature request ### Environment * Python version: 3.5.4 * NetBox version: 2.2.1 ### Description From the "Add a new device" page, when adding a device with a type declared as a Child device, it would be useful to have the option to assign it directly to a device with an empty slot. (i.e.: in the "location section" of the page, the rack face & position could probably switched to "a field showing the available devices with a free slot". Also, when looking at a device page ( /dcim/devices/xxxx/ ), when clicking on the green plus sign of a vacant slot to "install a device", it currently shows already created devices. Adding a "Create a new child device and assign to current parent" would be a real time saver. When we create a server, our current data model requires us to separate the management port (i.e. iDrac, ILOM, RMM, etc.) from the server but we attach it to the main server as a separate device. The reason for this is that the management port has it's own device name & OS and is separate from the main box. We have to create the server as a device, than create a management device, then go back to the server and assign it.
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 16:31:33 +01:00
adam closed this issue 2025-12-29 16:31:33 +01:00
adam commented 2025-12-29 16:31:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 18, 2018):

From the "Add a new device" page, when adding a device with a type declared as a Child device, it would be useful to have the option to assign it directly to a device with an empty slot.

While I agree that this would be a welcome improvement, it would require considerable development effort to implement, including:

  • Determining whether the selected device type is a child device
  • Dynamically altering the form to hide rack face and position, and show a list of parent devices
  • Populating available device bays in the form after selecting a parent device

I'll leave this open if someone wants to take a shot at it, but it's going to challenging with the current UI.

@jeremystretch commented on GitHub (Jul 18, 2018): > From the "Add a new device" page, when adding a device with a type declared as a Child device, it would be useful to have the option to assign it directly to a device with an empty slot. While I agree that this would be a welcome improvement, it would require considerable development effort to implement, including: * Determining whether the selected device type is a child device * Dynamically altering the form to hide rack face and position, and show a list of parent devices * Populating available device bays in the form after selecting a parent device I'll leave this open if someone wants to take a shot at it, but it's going to challenging with the current UI.
adam commented 2025-12-29 16:31:33 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Sep 7, 2020):

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.

@stale[bot] commented on GitHub (Sep 7, 2020): 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 16:31:33 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Sep 23, 2020):

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.

@stale[bot] commented on GitHub (Sep 23, 2020): 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#1335
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?