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

Custom field on device if role #4727

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

Originally created by @andershagman on GitHub (Apr 7, 2021).

NetBox version

v2.10.3

Feature type

Change to existing functionality

Proposed functionality

Be able to show/hide/disable custom fields on devices if they are of a certain role.

Use case

We have 5 different groups working in Netbox, Comm, Security, Storage, Appl.
We all have our own custom fields and some of them required. This results in having 10 different custom fields on a patch pannel with a demand on filling in hard drive size.

If combined with device role we can control where the filed will show up.

Database changes

Probably.

External dependencies

none

Originally created by @andershagman on GitHub (Apr 7, 2021). ### NetBox version v2.10.3 ### Feature type Change to existing functionality ### Proposed functionality Be able to show/hide/disable custom fields on devices if they are of a certain role. ### Use case We have 5 different groups working in Netbox, Comm, Security, Storage, Appl. We all have our own custom fields and some of them required. This results in having 10 different custom fields on a patch pannel with a demand on filling in hard drive size. If combined with device role we can control where the filed will show up. ### Database changes Probably. ### External dependencies none
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 19:19:55 +01:00
adam closed this issue 2025-12-29 19:19:56 +01:00
adam commented 2025-12-29 19:19:56 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 7, 2021):

That doesn't sound like it would scale very well. What specific changes to the model are you proposing? How would you declare the conditions under which each custom field would or would not be displayed?

@jeremystretch commented on GitHub (Apr 7, 2021): That doesn't sound like it would scale very well. What specific changes to the model are you proposing? How would you declare the conditions under which each custom field would or would not be displayed?
adam commented 2025-12-29 19:19:56 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 29, 2021):

I would love to see this as a feature as well, although I'm not sure how it could be implemented easily. Instead of just adding a custom field to the "device role" object , one would need to be able to add a custom field to a specific device role that already exists.

@ghost commented on GitHub (Apr 29, 2021): I would love to see this as a feature as well, although I'm not sure how it could be implemented easily. Instead of just adding a custom field to the "device role" object , one would need to be able to add a custom field to a specific device role that already exists.
adam commented 2025-12-29 19:19:56 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 17, 2021):

Closing this out as further detail concerning the proposed implementation has not been provided.

@jeremystretch commented on GitHub (May 17, 2021): Closing this out as further detail concerning the proposed implementation has not been provided.
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 pending closure status: revisions needed 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#4727
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?