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

Display child device interfaces on parent device interface list #773

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

Originally created by @pstanczak-vidscale on GitHub (Mar 16, 2017).

Feature request:
Ability to display child device interfaces on parent device interface list.
This way all interfaces from all device bays are displayed in parent device interface list, without the need to drill into individual bay child devices to see all the interfaces and circuits connected to them.
Child interfaces could be marked with a tag representing bay they belong to.

Originally created by @pstanczak-vidscale on GitHub (Mar 16, 2017). Feature request: Ability to display child device interfaces on parent device interface list. This way all interfaces from all device bays are displayed in parent device interface list, without the need to drill into individual bay child devices to see all the interfaces and circuits connected to them. Child interfaces could be marked with a tag representing bay they belong to.
adam added the type: feature label 2025-12-29 16:25:39 +01:00
adam closed this issue 2025-12-29 16:25:40 +01:00
adam commented 2025-12-29 16:25:40 +01:00
Author
Owner
Copy Link

@dhoutz commented on GitHub (Apr 5, 2017):

I'd like to second this request. Being able to see all interfaces on one page even when using child device bays would be very beneficial.

@dhoutz commented on GitHub (Apr 5, 2017): I'd like to second this request. Being able to see all interfaces on one page even when using child device bays would be very beneficial.
adam commented 2025-12-29 16:25:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 19, 2017):

I've thought about this a bit, but I'm going to reject this because I feel it convolutes what a device bay is intended to represent. A device bay holds a child device, which is an entirely separate logical entity; the components of one child have no relation to the components of another child within the same device. This is in contrast to the new type of relationship that we want to model in #824, which will represent modules within a device which each contain their own components.

I understand that in some situations it would be convenient to display all child device interfaces on one page, but in others it can lead to confusion, particularly when you consider the workflow of creating, editing, and deleting interfaces.

@jeremystretch commented on GitHub (Apr 19, 2017): I've thought about this a bit, but I'm going to reject this because I feel it convolutes what a device bay is intended to represent. A device bay holds a child device, which is an entirely separate logical entity; the components of one child have no relation to the components of another child within the same device. This is in contrast to the new type of relationship that we want to model in #824, which will represent modules within a device which each contain their own components. I understand that in some situations it would be convenient to display all child device interfaces on one page, but in others it can lead to confusion, particularly when you consider the workflow of creating, editing, and deleting interfaces.
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#773
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?