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 connection in batch #3002

New Issue
Closed
opened 2025-12-29 18:24:38 +01:00 by adam · 4 comments
adam commented 2025-12-29 18:24:38 +01:00
Owner
Copy Link

Originally created by @lmgonzalezl on GitHub (Nov 7, 2019).

Environment

  • NetBox version: v2.6.7

Proposed Functionality

In most cases the connection of the rear ports of a patch panel has a 1:1 relationwith a second panel. It would be interesting to be able to connect all tracer ports in batch.

Use Case

Batch all the trace ports of two patch panels. This is useful in structured cabling.

Example image

imagen

Database Changes

It is not necessary

Originally created by @lmgonzalezl on GitHub (Nov 7, 2019). <!-- NOTE: 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/forum/#!forum/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.6.7<!-- Example: 2.6.7 --> <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality In most cases the connection of the rear ports of a patch panel has a 1:1 relationwith a second panel. It would be interesting to be able to connect all tracer ports in batch. <!-- 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 Batch all the trace ports of two patch panels. This is useful in structured cabling. Example image ![imagen](https://user-images.githubusercontent.com/51785108/68391825-b7cb4500-0168-11ea-8b9d-7fc10212b01b.png) <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes It is not necessary
adam added the status: duplicate label 2025-12-29 18:24:38 +01:00
adam closed this issue 2025-12-29 18:24:38 +01:00
adam commented 2025-12-29 18:24:38 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 7, 2019):

This is a good idea, but it needs to be fleshed out. What is the proposed workflow? Let's say I have two panels created with all the appropriate front/rear ports. How do I connect all the rear ports together? What happens if some of the rear ports are already connected, or one panel has more than the other?

@jeremystretch commented on GitHub (Nov 7, 2019): This is a good idea, but it needs to be fleshed out. What is the proposed workflow? Let's say I have two panels created with all the appropriate front/rear ports. How do I connect all the rear ports together? What happens if some of the rear ports are already connected, or one panel has more than the other?
adam commented 2025-12-29 18:24:38 +01:00
Author
Owner
Copy Link

@lmgonzalezl commented on GitHub (Nov 7, 2019):

Proposed workflow
Visually I see it as follows:

I would keep the current format to select the rear ports but with the option to select both side a and side b and add a pop-up window that allows you to choose cable type, length, color, etc ... this would add it in a table.

Select rear ports on both sides
imagen

Pop-up window
imagen

Table
imagen

What happens if some of the rear ports are already connected, or one panel has more than the other?

As validation is done this will not be a problem because connected ports already are disabled from the selection.

@lmgonzalezl commented on GitHub (Nov 7, 2019): **Proposed workflow** Visually I see it as follows: I would keep the current format to select the rear ports but with the option to select both side a and side b and add a pop-up window that allows you to choose cable type, length, color, etc ... this would add it in a table. **Select rear ports on both sides** ![imagen](https://user-images.githubusercontent.com/51785108/68421585-d3514280-019e-11ea-824c-47ea701f448e.png) **Pop-up window** ![imagen](https://user-images.githubusercontent.com/51785108/68421750-1f9c8280-019f-11ea-8ff1-298042404940.png) **Table** ![imagen](https://user-images.githubusercontent.com/51785108/68421769-2aefae00-019f-11ea-860a-3cf2761143d4.png) **What happens if some of the rear ports are already connected, or one panel has more than the other?** As validation is done this will not be a problem because connected ports already are disabled from the selection.
adam commented 2025-12-29 18:24:39 +01:00
Author
Owner
Copy Link

@lmgonzalezl commented on GitHub (Nov 8, 2019):

I see that there is another issue (#2855) where this has been discussed. In any case I add a new option to implement it.

@lmgonzalezl commented on GitHub (Nov 8, 2019): I see that there is another issue (#[2855](https://github.com/netbox-community/netbox/issues/2855)) where this has been discussed. In any case I add a new option to implement it.
adam commented 2025-12-29 18:24:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 11, 2019):

Marking this as a duplicate of #2855. Please feel free to copy your comment above there.

@jeremystretch commented on GitHub (Nov 11, 2019): Marking this as a duplicate of #2855. Please feel free to copy your comment above there.
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
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#3002
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?