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

Group parent/child devices in tenant view #7109

New Issue
Closed
opened 2025-12-29 20:19:21 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:19:21 +01:00
Owner
Copy Link

Originally created by @2code4me on GitHub (Oct 14, 2022).

NetBox version

3.3.5

Feature type

New functionality

Proposed functionality

Hi, would be possible to add a function (for example adding a checkbox) to group child devices to their parent to count them as a unique device in tenants view?

Use case

Example:

I'm adding a Netapp E2860 of a customer.
The device is a storage chassis with 4 bays (well 6 to be honest, as 2 are used for fans).
2 bays used for PSU and 2 bays used for storage controller.
If I deploy 1 E2860 chassis (Parent) and add to it 2 PSU and 2 Controllers (Childs), when I take a look to the customer tenant I see he has 5 Devices.
That, yes, formerly is correct but usually it has to be considered 1 single storage device and only if I want to go deeper in details I can see the controllers and PSU.

Maybe this function could be managed with a flag in child creation, something like "Link this device to its parent for device count" so that in other cases, like a blade chassis with different server, I can leave the flag unselected and each device can be counted as one.

Database changes

Probably a new flag button is needed. Don't know which modification are needed at database level.

External dependencies

No response

Originally created by @2code4me on GitHub (Oct 14, 2022). ### NetBox version 3.3.5 ### Feature type New functionality ### Proposed functionality Hi, would be possible to add a function (for example adding a checkbox) to group child devices to their parent to count them as a unique device in tenants view? ### Use case Example: I'm adding a Netapp E2860 of a customer. The device is a storage chassis with 4 bays (well 6 to be honest, as 2 are used for fans). 2 bays used for PSU and 2 bays used for storage controller. If I deploy 1 E2860 chassis (Parent) and add to it 2 PSU and 2 Controllers (Childs), when I take a look to the customer tenant I see he has 5 Devices. That, yes, formerly is correct but usually it has to be considered 1 single storage device and only if I want to go deeper in details I can see the controllers and PSU. Maybe this function could be managed with a flag in child creation, something like "Link this device to its parent for device count" so that in other cases, like a blade chassis with different server, I can leave the flag unselected and each device can be counted as one. ### Database changes Probably a new flag button is needed. Don't know which modification are needed at database level. ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:19:21 +01:00
adam closed this issue 2025-12-29 20:19:21 +01:00
adam commented 2025-12-29 20:19:22 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 14, 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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 14, 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:19:22 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 29, 2022):

What you're describing is the intended behavior; you see five devices listed for the customer because five devices in fact exist. I'm not familiar with the particular hardware you mention, but it might be more appropriate for your use case to employ modules rather than child devices, which do not appear under the devices list.

@jeremystretch commented on GitHub (Dec 29, 2022): What you're describing is the intended behavior; you see five devices listed for the customer because five devices in fact exist. I'm not familiar with the particular hardware you mention, but it might be more appropriate for your use case to employ [modules](https://docs.netbox.dev/en/stable/models/dcim/module/) rather than child devices, which do not appear under the devices list.
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#7109
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?