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

Control for visibility of custom field group #10366

New Issue
Closed
opened 2025-12-29 21:30:32 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:30:32 +01:00
Owner
Copy Link

Originally created by @craigmoscardini on GitHub (Oct 16, 2024).

NetBox version

4.0.9

Feature type

Change to existing functionality

Triage priority

N/A

Proposed functionality

Although individual custom field visibility can be controlled based on whether data is present, when lots of custom fields are present the user must establish which are required themselves.

The proposal is to control visibility of a custom field group, probably in a similar structure to custom validators.

Visibility of the group would be set based on the value of another field within that object. For example a custom field group called "Mast Site Information" could be set to visible or not based on a custom field Boolean value. The same could be extended to any field for example a particular tag being present.

This would add most value at a site and device level, but in theory could be extended to any object.

Use case

Filtering visibility of custom field groups to present data only relevant to the context of the object

Database changes

None

External dependencies

None

Originally created by @craigmoscardini on GitHub (Oct 16, 2024). ### NetBox version 4.0.9 ### Feature type Change to existing functionality ### Triage priority N/A ### Proposed functionality Although individual custom field visibility can be controlled based on whether data is present, when lots of custom fields are present the user must establish which are required themselves. The proposal is to control visibility of a custom field group, probably in a similar structure to custom validators. Visibility of the group would be set based on the value of another field within that object. For example a custom field group called "Mast Site Information" could be set to visible or not based on a custom field Boolean value. The same could be extended to any field for example a particular tag being present. This would add most value at a site and device level, but in theory could be extended to any object. ### Use case Filtering visibility of custom field groups to present data only relevant to the context of the object ### Database changes None ### External dependencies None
adam added the type: featurenetbox labels 2025-12-29 21:30:32 +01:00
adam closed this issue 2025-12-29 21:30:32 +01:00
adam commented 2025-12-29 21:30:32 +01:00
Author
Owner
Copy Link

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

While I appreciate the use case, this seems like it's pushing the intended use case of custom fields a bit too far. If you've reached the point where you need to conditionally display a set of custom fields, a dedicated data model delivered via a plugin would almost certainly be the preferred solution.

@jeremystretch commented on GitHub (Feb 6, 2025): While I appreciate the use case, this seems like it's pushing the intended use case of custom fields a bit too far. If you've reached the point where you need to conditionally display a set of custom fields, a dedicated data model delivered via a plugin would almost certainly be the preferred solution.
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 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#10366
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?