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

Limit the visibility of unused custom fields in the GUI #5009

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

Originally created by @jcralbino on GitHub (Jun 17, 2021).

NetBox version

v2.11.4

Feature type

Change to existing functionality

Proposed functionality

Currently we can associate custom fields to almost any object in Netbox.
After they are created they will be shown in the webinterface of that object.

This would be valid for all custom fields that do not have the flag required enabled.

I propose to only show the custom fields being used ( not empty) when viewing that specific object.

Use case

Reduces the noise on the information provided to the user, when viewing a device.

When editing the device all options would be there

Database changes

none

External dependencies

none

Originally created by @jcralbino on GitHub (Jun 17, 2021). ### NetBox version v2.11.4 ### Feature type Change to existing functionality ### Proposed functionality Currently we can associate custom fields to almost any object in Netbox. After they are created they will be shown in the webinterface of that object. This would be valid for all custom fields that do not have the flag required enabled. I propose to only show the custom fields being used ( not empty) when viewing that specific object. ### Use case Reduces the noise on the information provided to the user, when viewing a device. When editing the device all options would be there ### Database changes none ### External dependencies none
adam added the type: featurestatus: duplicate labels 2025-12-29 19:23:08 +01:00
adam closed this issue 2025-12-29 19:23:08 +01:00
adam commented 2025-12-29 19:23:08 +01:00
Author
Owner
Copy Link

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

There is already an open issue for this, which you have commented on: #6296.

@jeremystretch commented on GitHub (Jun 17, 2021): There is already an open issue for this, which you have commented on: #6296.
adam commented 2025-12-29 19:23:09 +01:00
Author
Owner
Copy Link

@jcralbino commented on GitHub (Jun 18, 2021):

Hello Jeremy. I created this one to have the scope more defined as the previous one had one different initial request.
In the end I am ok to close this If we can implement the feature in the other one

@jcralbino commented on GitHub (Jun 18, 2021): Hello Jeremy. I created this one to have the scope more defined as the previous one had one different initial request. In the end I am ok to close this If we can implement the feature in the other one
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 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#5009
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?