Cable Edit #4113

Closed
opened 2025-12-29 18:33:12 +01:00 by adam · 1 comment
Owner

Originally created by @Paktosan on GitHub (Sep 17, 2020).

Environment

  • Python version: Unknown
  • NetBox version: 2.9.3

Proposed Functionality

Ability to change connected device when editing a cable.

Use Case

It sometimes happens that we move one end of a cable from one device to another while keeping the other side the same.
Currently one has to delete the old and set up a new cable filling out all details again.

Database Changes

None as far as I am aware.

External Dependencies

None as far as I am aware.

Originally created by @Paktosan on GitHub (Sep 17, 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 * NetBox version: 2.9.3 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Ability to change connected device when editing a cable. <!-- 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 It sometimes happens that we move one end of a cable from one device to another while keeping the other side the same. Currently one has to delete the old and set up a new cable filling out all details again. <!-- 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 None as far as I am aware. <!-- 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 as far as I am aware.
adam added the status: duplicate label 2025-12-29 18:33:12 +01:00
adam closed this issue 2025-12-29 18:33:13 +01:00
Author
Owner

@jeremystretch commented on GitHub (Sep 17, 2020):

Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #4881 for further discussion.

@jeremystretch commented on GitHub (Sep 17, 2020): Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #4881 for further discussion.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4113