starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Ability to 'hide' fields from models #8940

New Issue
Closed
opened 2025-12-29 20:43:07 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:43:07 +01:00
Owner
Copy Link

Originally created by @PieterL75 on GitHub (Dec 10, 2023).

NetBox version

v3.6.6

Feature type

Data model extension

Proposed functionality

My proposal is providing an ability to hide (non-required) fields from the view, table and editform of a model.
This could be done through settings on the configuration.py, or even better through the admin module.

Use case

As netbox grows, more and more field are added to the models.
Most of them have a very generic purpose, and are relevant.
Other are very specific for certain use cases or data modeling and not relevant to oher.
For ex, the GPS coordinates in devices. We don't use those, as all of our gear is in a datacenter with racks.

New FR like https://github.com/netbox-community/netbox/issues/14389 add extra fields to models.
Having that many fields confuses users and are not helping to make the editform shorter and quicker to fill in.

Database changes

Extra table that keeps track of what fields should be enabled for what models

External dependencies

No response

Originally created by @PieterL75 on GitHub (Dec 10, 2023). ### NetBox version v3.6.6 ### Feature type Data model extension ### Proposed functionality My proposal is providing an ability to hide (non-required) fields from the view, table and editform of a model. This could be done through settings on the configuration.py, or even better through the admin module. ### Use case As netbox grows, more and more field are added to the models. Most of them have a very generic purpose, and are relevant. Other are very specific for certain use cases or data modeling and not relevant to oher. For ex, the GPS coordinates in devices. We don't use those, as all of our gear is in a datacenter with racks. New FR like https://github.com/netbox-community/netbox/issues/14389 add extra fields to models. Having that many fields confuses users and are not helping to make the editform shorter and quicker to fill in. ### Database changes Extra table that keeps track of what fields should be enabled for what models ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:43:07 +01:00
adam closed this issue 2025-12-29 20:43:07 +01:00
adam commented 2025-12-29 20:43:08 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 26, 2023):

I'm sorry, but the development and maintenance burden to support something like this far exceeds any perceived value, so this is going to be a "no." If you have no use for certain fields, simply don't use them. NetBox is a highly customizable tool, but we have to draw the line somewhere, and this is it.

If you really need to remove core fields for some reason, you'll need to fork the code base yourself to make (and be responsible for) those changes.

@jeremystretch commented on GitHub (Dec 26, 2023): I'm sorry, but the development and maintenance burden to support something like this _far_ exceeds any perceived value, so this is going to be a "no." If you have no use for certain fields, simply don't use them. NetBox is a highly customizable tool, but we have to draw the line somewhere, and this is it. If you _really_ need to remove core fields for some reason, you'll need to fork the code base yourself to make (and be responsible for) those changes.
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 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#8940
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?