Multiple Mark/Dismark connected (Treat as if a cable is connected) #7037

Closed
opened 2025-12-29 19:48:11 +01:00 by adam · 2 comments
Owner

Originally created by @ShellBoyAFK on GitHub (Sep 28, 2022).

NetBox version

v3.3.4

Feature type

Change to existing functionality

Proposed functionality

It would be nice if the disconnect button would also solve Marked as Connected Cables

Use case

I often mark several front or rear ports as connected via the collective edit function.

You can obviously select all of them as "Marked as Connect", but you can't unmark them.

Database changes

No response

External dependencies

No response

Originally created by @ShellBoyAFK on GitHub (Sep 28, 2022). ### NetBox version v3.3.4 ### Feature type Change to existing functionality ### Proposed functionality It would be nice if the disconnect button would also solve Marked as Connected Cables ### Use case I often mark several front or rear ports as connected via the collective edit function. You can obviously select all of them as "Marked as Connect", but you can't unmark them. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 19:48:11 +01:00
adam closed this issue 2025-12-29 19:48:11 +01:00
Author
Owner

@jeremystretch commented on GitHub (Sep 28, 2022):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (Sep 28, 2022): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
Author
Owner

@jeremystretch commented on GitHub (Oct 5, 2022):

Closing this as there's been no further reply.

@jeremystretch commented on GitHub (Oct 5, 2022): Closing this as there's been no further reply.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7037