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

Please implement moving ends of a cable #3881

New Issue
Closed
opened 2025-12-29 18:31:45 +01:00 by adam · 10 comments
adam commented 2025-12-29 18:31:45 +01:00
Owner
Copy Link

Originally created by @ThomasGiger on GitHub (Jul 23, 2020).

Environment

  • Python version: unknown - using a pre-installed system
  • NetBox version: 2.8.7

Proposed Functionality

Haven't found a way to move one end of a cable from one port/interface of a device to another one. The cable needs to be deleted and another one needs to be added, as it seems.

Use Case

One could have made a mistake while adding a cable or the change is to reflect something that happens in pratice - it would be a real time-saver if one end or both of a cable could be reassigned to some other port/interface without havin to deleted and re-add the cable, which is a some work at least if you care about type, color, label and all those details.

Database Changes

This appears to be a UI enhancement, so none expected.

External Dependencies

None.

Originally created by @ThomasGiger on GitHub (Jul 23, 2020). <!-- 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/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 * Python version: unknown - using a pre-installed system * NetBox version: 2.8.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 Haven't found a way to move one end of a cable from one port/interface of a device to another one. The cable needs to be deleted and another one needs to be added, as it seems. <!-- 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 One could have made a mistake while adding a cable or the change is to reflect something that happens in pratice - it would be a real time-saver if one end or both of a cable could be reassigned to some other port/interface without havin to deleted and re-add the cable, which is a some work at least if you care about type, color, label and all those details. <!-- 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 This appears to be a UI enhancement, so none expected. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None.
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 18:31:45 +01:00
adam closed this issue 2025-12-29 18:31:45 +01:00
adam commented 2025-12-29 18:31:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 24, 2020):

Blocked by #4900

@jeremystretch commented on GitHub (Jul 24, 2020): Blocked by #4900
adam commented 2025-12-29 18:31:46 +01:00
Author
Owner
Copy Link

@raddessi commented on GitHub (Jan 27, 2021):

This is no longer blocked with the addition of 4900 correct?

@raddessi commented on GitHub (Jan 27, 2021): This is no longer blocked with the addition of 4900 correct?
adam commented 2025-12-29 18:31:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 13, 2021):

Open for volunteers under v2.11.

@jeremystretch commented on GitHub (Apr 13, 2021): Open for volunteers under v2.11.
adam commented 2025-12-29 18:31:46 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 13, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jun 13, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 18:31:46 +01:00
Author
Owner
Copy Link

@eronlloyd commented on GitHub (Jun 13, 2021):

I'd love to see this get implemented, and would donate towards a bounty if needed.

@eronlloyd commented on GitHub (Jun 13, 2021): I'd love to see this get implemented, and would donate towards a bounty if needed.
adam commented 2025-12-29 18:31:46 +01:00
Author
Owner
Copy Link

@hellerve commented on GitHub (Jul 27, 2021):

We have an implementation for this in a plugin that I’d be happy to try to port to the core of NetBox instead. Making it part of the core would also enable different interactions (via the tables directly rather than the cable detail view, which is how it currently happens in the plugin).

I’d be happy to contribute the initial version and then iteratively refine the interface based on the desired UI/UX.

@hellerve commented on GitHub (Jul 27, 2021): We have an implementation for this in a plugin that I’d be happy to try to port to the core of NetBox instead. Making it part of the core would also enable different interactions (via the tables directly rather than the cable detail view, which is how it currently happens in the plugin). I’d be happy to contribute the initial version and then iteratively refine the interface based on the desired UI/UX.
adam commented 2025-12-29 18:31:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 4, 2021):

@hellerve Cool. I'm going to assign this to you for a PR whenever you have time. Let's base it off the v3.0 UI to avoid any rework, since v3.0 should be out pretty soon anyway. (Please work off the feature branch for now.)

@jeremystretch commented on GitHub (Aug 4, 2021): @hellerve Cool. I'm going to assign this to you for a PR whenever you have time. Let's base it off the v3.0 UI to avoid any rework, since v3.0 should be out pretty soon anyway. (Please work off the `feature` branch for now.)
adam commented 2025-12-29 18:31:46 +01:00
Author
Owner
Copy Link

@hellerve commented on GitHub (Aug 5, 2021):

I added a (working) draft containing the work I had at hand. Let me know whether the UX works for y’all!

@hellerve commented on GitHub (Aug 5, 2021): I added a (working) draft containing the work I had at hand. Let me know whether the UX works for y’all!
adam commented 2025-12-29 18:31:46 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 25, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 25, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 18:31:46 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 26, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jan 26, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: needs owner 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#3881
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?