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

User defined port-types #5641

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

Originally created by @vbarelds on GitHub (Nov 10, 2021).

NetBox version

v3.0.8

Feature type

Change to existing functionality

Proposed functionality

For the user to be able to add user-defined port types.
Also asked in #4371 but this request has been closed without a proper follow up.

Use case

In my case there is a device with multiple DVI inputs and outputs.
Since there is no correct port-type that can be selected the port-type cant be seen as a "source of truth".

Users are able to create a work around with custom field for Front and Rear ports. But this is not ideal since there are two port-type fields when using this work around

Also in the future there can be an new kind of port-types, you can't expect a user to wait until the desired port-type is available trough an update. So it would benefit the user to be able to add custom port-types.

Users should be able to add port-types in the same way tags are added. And when added selectable trough the port-type drop down menu.

Database changes

A table for user-defined port-types

External dependencies

None

Originally created by @vbarelds on GitHub (Nov 10, 2021). ### NetBox version v3.0.8 ### Feature type Change to existing functionality ### Proposed functionality For the user to be able to add user-defined port types. Also asked in **#4371** but this request has been closed without a proper follow up. ### Use case In my case there is a device with multiple DVI inputs and outputs. Since there is no correct port-type that can be selected the port-type cant be seen as a "source of truth". **_Users are able to create a work around with custom field for Front and Rear ports. But this is not ideal since there are two port-type fields when using this work around_** Also in the future there can be an new kind of port-types, you can't expect a user to wait until the desired port-type is available trough an update. So it would benefit the user to be able to add custom port-types. Users should be able to add port-types in the same way tags are added. And when added selectable trough the port-type drop down menu. ### Database changes A table for user-defined port-types ### External dependencies None
adam added the type: feature label 2025-12-29 19:30:35 +01:00
adam closed this issue 2025-12-29 19:30:35 +01:00
adam commented 2025-12-29 19:30:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 10, 2021):

Please see this answer in the FAQ regarding why NetBox doesn't permit user-defined device component types.

In my case there is a device with multiple DVI inputs and outputs.

NetBox's focus is network infrastructure; video is out of scope for the product.

@jeremystretch commented on GitHub (Nov 10, 2021): Please see [this answer in the FAQ](https://github.com/netbox-community/netbox/wiki/Frequently-Asked-Questions#how-can-i-add-new-interface-types) regarding why NetBox doesn't permit user-defined device component types. > In my case there is a device with multiple DVI inputs and outputs. NetBox's focus is network infrastructure; video is out of scope for the product.
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#5641
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?