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

Add Support for Parent Device Roles #7884

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

Originally created by @djmelik on GitHub (Apr 8, 2023).

NetBox version

v3.4.7

Feature type

Data model extension

Proposed functionality

I would like for Netbox to be able to support parent-child relationships in the context of Device Roles. It would be nice to be able to nest device role types for greater granularity and organization.

Use case

Currently, we have many different router and switch device role types. For instance; we have Border Router, Peering Router, Access Router, Core Router, Spine Router, Leaf Router, etc. It would be nice to be able to create a parent "Router" Device Role parent type, and set all granular router device roles as children. In other words, nest Access Router, Border Router, Peering Router, etc under Router.

This would significantly help with both filtering and just general organization.

Database changes

Unfortunately, I am not a developer; I do not know how to meaningfully answer this question.

External dependencies

N/A

Originally created by @djmelik on GitHub (Apr 8, 2023). ### NetBox version v3.4.7 ### Feature type Data model extension ### Proposed functionality I would like for Netbox to be able to support parent-child relationships in the context of Device Roles. It would be nice to be able to nest device role types for greater granularity and organization. ### Use case Currently, we have many different router and switch device role types. For instance; we have Border Router, Peering Router, Access Router, Core Router, Spine Router, Leaf Router, etc. It would be nice to be able to create a parent "Router" Device Role parent type, and set all granular router device roles as children. In other words, nest Access Router, Border Router, Peering Router, etc under Router. This would significantly help with both filtering and just general organization. ### Database changes Unfortunately, I am not a developer; I do not know how to meaningfully answer this question. ### External dependencies N/A
adam added the type: feature label 2025-12-29 20:29:30 +01:00
adam closed this issue 2025-12-29 20:29:30 +01:00
adam commented 2025-12-29 20:29:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 4, 2023):

IMO this makes sense, but first we need to figure out what we're doing with MPTT, which is what's currently in place for all self-nesting models. I'm going to mark this as blocked by #6587 / #11421.

@jeremystretch commented on GitHub (May 4, 2023): IMO this makes sense, but first we need to figure out what we're doing with MPTT, which is what's currently in place for all self-nesting models. ~I'm going to mark this as blocked by #6587 / #11421.~
adam commented 2025-12-29 20:29:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 10, 2023):

Blocked by #12552

@jeremystretch commented on GitHub (May 10, 2023): Blocked by #12552
adam commented 2025-12-29 20:29:31 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (May 11, 2023):

Duplicate of #6290

@DanSheps commented on GitHub (May 11, 2023): Duplicate of #6290
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#7884
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?