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

Add additional options to 'rear ports', 'front ports', and 'power' types #6332

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

Originally created by @ghost on GitHub (Apr 10, 2022).

Originally assigned to: @bluikko on GitHub.

NetBox version

v3.2.0

Feature type

Change to existing functionality

Proposed functionality

Type 'other' is available for interfaces, but no such generalized option exists for 'front port', 'rear port', or 'power' connector types.
A list of every single possible connector type for these connections would not be feasible, so unless users have the ability to add options themselves (which is outside the scope of this request) the next best option is to add an 'other' type to each of those options drop down lists.

Use case

There are many more connector types available than what is listed for rear port, front port, and power type connections. Adding an 'other' option to these drop down lists would allow users to select something if their particular connector is not listed, rather than not filling in the data at all.

Database changes

No response

External dependencies

No response

Originally created by @ghost on GitHub (Apr 10, 2022). Originally assigned to: @bluikko on GitHub. ### NetBox version v3.2.0 ### Feature type Change to existing functionality ### Proposed functionality Type 'other' is available for interfaces, but no such generalized option exists for 'front port', 'rear port', or 'power' connector types. A list of every single possible connector type for these connections would not be feasible, so unless users have the ability to add options themselves (which is outside the scope of this request) the next best option is to add an 'other' type to each of those options drop down lists. ### Use case There are many more connector types available than what is listed for rear port, front port, and power type connections. Adding an 'other' option to these drop down lists would allow users to select something if their particular connector is not listed, rather than not filling in the data at all. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:39:31 +01:00
adam closed this issue 2025-12-29 19:39:31 +01:00
adam commented 2025-12-29 19:39:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 10, 2022):

A list of every single possible connector type for these connections would not be feasible

Sure it is. We see proposals for new types occasionally, but what exists in NetBox today is fairly exhaustive. There is of course a finite set of such hardware in common use, and this approach has enabled us to compile the massive community-sourced device type library.

Proposals to add real, well-defined component types that have not yet been added are welcomed and appreciated. Still, adding "other" as a catch-all is fine too.

@jeremystretch commented on GitHub (Apr 10, 2022): > A list of every single possible connector type for these connections would not be feasible Sure it is. We see proposals for new types occasionally, but what exists in NetBox today is fairly exhaustive. There is of course a finite set of such hardware in common use, and this approach has enabled us to compile the massive community-sourced [device type library](https://github.com/netbox-community/devicetype-library). Proposals to add real, well-defined component types that have not yet been added are welcomed and appreciated. Still, adding "other" as a catch-all is fine too.
adam commented 2025-12-29 19:39:31 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 1, 2022):

How did https://github.com/netbox-community/netbox/issues/9192 make it into 3.2.2 before this one?

@ghost commented on GitHub (May 1, 2022): How did https://github.com/netbox-community/netbox/issues/9192 make it into 3.2.2 before this one?
adam commented 2025-12-29 19:39:32 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (May 1, 2022):

@cyr0nk0r if you hover over the status: needs owner label you will see the description:

This issue is tentatively accepted pending a volunteer committed to its implementation

A volunteer implemented the suggested change in the issue you linked. That's why it was added.

@kkthxbye-code commented on GitHub (May 1, 2022): @cyr0nk0r if you hover over the `status: needs owner` label you will see the description: >This issue is tentatively accepted pending a volunteer committed to its implementation A volunteer implemented the suggested change in the issue you linked. That's why it was added.
adam commented 2025-12-29 19:39:32 +01:00
Author
Owner
Copy Link

@bluikko commented on GitHub (May 18, 2022):

Seems like a very simple change, hope I got it right in the PR.

@bluikko commented on GitHub (May 18, 2022): Seems like a very simple change, hope I got it right in the PR.
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: accepted 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#6332
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?