Add Filtering-Based Scoping for Custom Fields #268

Closed
opened 2026-04-05 16:24:04 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @Thorndelaus on 2/28/2026

NetBox version

v4.5.3

Feature type

Data model extension

Proposed functionality

Introduce object-level scoping for Custom Fields by allowing to define filter conditions that determine which objects a custom field applies to.

Currently, custom fields can only be scoped to a object type (e.g., DCIM > Device). This proposal extends the data model to allow optional filtering within that content type (e.g., only devices with a specific device role).

Use case

Without this feature objects display irrelevant custom fields that do not apply to their function.
Users may populate fields on inappropriate device types, leading to incorrect or misleading data.
It becomes unclear whether an empty field is not applicable, or is missing required data.

This feature would provide a cleaner, context-aware UI experience and decrease risk of incorrect or inconsistent data entry.

Database changes

No response

External dependencies

No response

*Originally created by @Thorndelaus on 2/28/2026* ### NetBox version v4.5.3 ### Feature type Data model extension ### Proposed functionality Introduce object-level scoping for Custom Fields by allowing to define filter conditions that determine which objects a custom field applies to. Currently, custom fields can only be scoped to a object type (e.g., DCIM > Device). This proposal extends the data model to allow optional filtering within that content type (e.g., only devices with a specific device role). ### Use case Without this feature objects display irrelevant custom fields that do not apply to their function. Users may populate fields on inappropriate device types, leading to incorrect or misleading data. It becomes unclear whether an empty field is not applicable, or is missing required data. This feature would provide a cleaner, context-aware UI experience and decrease risk of incorrect or inconsistent data entry. ### Database changes _No response_ ### External dependencies _No response_
Sign in to join this conversation.
No Label netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature 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#268