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

Support custom fields on interfaces at the device type level #7622

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

Originally created by @ghost on GitHub (Feb 8, 2023).

NetBox version

v3.4.4

Feature type

Data model extension

Proposed functionality

Netbox has previously added support for creating custom fields at the interface level for devices. However these are not supported at the device type level. I.E. interfaces on device type cannot have custom interfaces.

Use case

We track several additional fields such as NIC chipset, NIC PCIe address, etc that would be well suited to track at the device type level since they are associated with different device models. Currently we have to manually populate those fields each time we create a new device of that device type.

Database changes

No response

External dependencies

No response

Originally created by @ghost on GitHub (Feb 8, 2023). ### NetBox version v3.4.4 ### Feature type Data model extension ### Proposed functionality Netbox has previously added support for creating custom fields at the interface level for devices. However these are not supported at the device type level. I.E. interfaces on device type cannot have custom interfaces. ### Use case We track several additional fields such as NIC chipset, NIC PCIe address, etc that would be well suited to track at the device type level since they are associated with different device models. Currently we have to manually populate those fields each time we create a new device of that device type. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: duplicate labels 2025-12-29 20:26:08 +01:00
adam closed this issue 2025-12-29 20:26:11 +01:00
adam commented 2025-12-29 20:26:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 8, 2023):

Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #9243 for further discussion.

@jeremystretch commented on GitHub (Feb 8, 2023): Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #9243 for further discussion.
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#7622
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?