Allow Device Roles to have multiple parent roles #1416

New Issue

MrUnknownDE · 2026-04-06T01:06:10+02:00

MrUnknownDE commented

2026-04-06 01:06:10 +02:00

Originally created by @whtkam on 8/21/2025

NetBox version

v4.3.6

Feature type

Data model extension

Proposed functionality

Currently, a Device Role in NetBox can only be assigned a single parent role.
I would like to request the ability to assign multiple parent roles to a Device Role.

Use case

We have a parent device role Switch and another parent role Encryption.
A device that is an Encryption Switch logically belongs under both roles.
With the current model, it can only inherit from one parent role, which makes filtering less flexible.
If multiple parent roles were supported, the Encryption Switch would show up in both views when filtering by Switch or by Encryption.

A similar concept already exists with Contacts, where a single contact can belong to multiple groups. This flexible model would also be very useful for Device Roles.

This would improve classification and filtering, especially for devices that naturally span multiple categories.

Database changes

No response

External dependencies

No response

*Originally created by @whtkam on 8/21/2025* ### NetBox version v4.3.6 ### Feature type Data model extension ### Proposed functionality Currently, a Device Role in NetBox can only be assigned a single parent role. I would like to request the ability to assign multiple parent roles to a Device Role. ### Use case We have a parent device role Switch and another parent role Encryption. A device that is an Encryption Switch logically belongs under both roles. With the current model, it can only inherit from one parent role, which makes filtering less flexible. If multiple parent roles were supported, the Encryption Switch would show up in both views when filtering by Switch or by Encryption. A similar concept already exists with Contacts, where a single contact can belong to multiple groups. This flexible model would also be very useful for Device Roles. This would improve classification and filtering, especially for devices that naturally span multiple categories. ### Database changes _No response_ ### External dependencies _No response_

MrUnknownDE closed this issue

2026-04-06 01:06:10 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#1416