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 Device role parent/child support like regions #4835

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

Originally created by @JulijusBertasius on GitHub (Apr 27, 2021).

NetBox version

v2.11.0

Feature type

Data model extension

Proposed functionality

Allow assign Device role to Parent Device role, like in Regions

Use case

In my organisation, we use a lot of different device roles and we would like to be able, to group those roles to network, storage and etc. parent device roles. Just like in regions model.

Database changes

Device role model, would have new field Parent.

External dependencies

None

Originally created by @JulijusBertasius on GitHub (Apr 27, 2021). ### NetBox version v2.11.0 ### Feature type Data model extension ### Proposed functionality Allow assign `Device role` to `Parent` `Device role`, like in `Regions` ### Use case In my organisation, we use a lot of different device roles and we would like to be able, to group those roles to network, storage and etc. parent device roles. Just like in regions model. ### Database changes `Device role` model, would have new field `Parent`. ### External dependencies None
adam added the type: featurestatus: duplicatenetbox labels 2025-12-29 19:21:04 +01:00
adam closed this issue 2025-12-29 19:21:04 +01:00
adam commented 2025-12-29 19:21:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 8, 2022):

Marking this as blocked by #6587. I want to ensure we have a clear stance on the future of our MPTT approach before implementing it for any more models.

@jeremystretch commented on GitHub (Apr 8, 2022): Marking this as blocked by #6587. I want to ensure we have a clear stance on the future of our MPTT approach before implementing it for any more models.
adam commented 2025-12-29 19:21:05 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Jan 12, 2023):

With #6587 slated for v3.5, could we slate this for v3.5 or v3.6

@ryanmerolle commented on GitHub (Jan 12, 2023): With #6587 slated for v3.5, could we slate this for v3.5 or v3.6
adam commented 2025-12-29 19:21:05 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Jan 12, 2023):

Not to open Pandora's box, but would we look to set a uniform setup for IPAM roles as well?

@ryanmerolle commented on GitHub (Jan 12, 2023): Not to open Pandora's box, but would we look to set a uniform setup for IPAM roles as well?
adam commented 2025-12-29 19:21:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 12, 2023):

With #6587 slated for v3.5, could we slate this for v3.5 or v3.6

If we get it implemented, sure. I think right now we're leaning toward #11421 as an alternative approach, but either way we still need to provide viability to replace MPTT.

@jeremystretch commented on GitHub (Jan 12, 2023): > With #6587 slated for v3.5, could we slate this for v3.5 or v3.6 If we get it _implemented_, sure. I think right now we're leaning toward #11421 as an alternative approach, but either way we still need to provide viability to replace MPTT.
adam commented 2025-12-29 19:21:06 +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 19:21:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 27, 2023):

Unblocking this as it doesn't seem like we'll be replacing MPTT anytime soon.

@jeremystretch commented on GitHub (Dec 27, 2023): Unblocking this as it doesn't seem like we'll be replacing MPTT anytime soon.
adam commented 2025-12-29 19:21:07 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 27, 2024):

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 (Mar 27, 2024): 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 19:21:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 11, 2025):

Folding this into FR #18245, which provides a more detailed implementation plan.

@jeremystretch commented on GitHub (Feb 11, 2025): Folding this into FR #18245, which provides a more detailed implementation plan.
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 netbox status: duplicate 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#4835
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?