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

Cable Bulk Import additional info #4321

New Issue
Closed
opened 2025-12-29 18:34:44 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:34:44 +01:00
Owner
Copy Link

Originally created by @elixdreamer on GitHub (Dec 1, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • NetBox version: v2.9.9

Proposed Functionality

Add some additional info to the CSV Field Options for side_a_type and side_b_type.
The info will include all possible ports that can be used to import Bulk cables.
After some digging in the code I found the following list, not sure if it is complete.
'consoleport', 'consoleserverport', 'interface', 'frontport', 'rearport', 'circuittermination'

Use Case

In a bulk cable import that was meant for Rear to rear ports I was unable to find the correct type that need to be used.
after creating a case it came to my knowledge that i had to use rearport iso Rear Port or dcim.rearport.
Probably some confusion could be for other interfaces. I have seen multiple issue reported the interface should be set with lower i.

Originally created by @elixdreamer on GitHub (Dec 1, 2020). Originally assigned to: @jeremystretch on GitHub. <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/g/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * NetBox version: v2.9.9 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Add some additional info to the CSV Field Options for side_a_type and side_b_type. The info will include all possible ports that can be used to import Bulk cables. After some digging in the code I found the following list, not sure if it is complete. `'consoleport', 'consoleserverport', 'interface', 'frontport', 'rearport', 'circuittermination'` <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case In a bulk cable import that was meant for Rear to rear ports I was unable to find the correct type that need to be used. after creating a case it came to my knowledge that i had to use `rearport` iso `Rear Port` or `dcim.rearport`. Probably some confusion could be for other interfaces. I have seen multiple issue reported the `interface` should be set with lower i.
adam added the status: acceptedtype: feature labels 2025-12-29 18:34:44 +01:00
adam closed this issue 2025-12-29 18:34:44 +01:00
adam commented 2025-12-29 18:34:45 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 2, 2020):

This will be added in v2.10.

@jeremystretch commented on GitHub (Dec 2, 2020): This will be added in v2.10.
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#4321
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?