-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cables/UI: Unable to change from front to rear while editing cable #13278
Comments
More broadly , same applies if you need to change termination type (front , rear , interface etc.) of one end you have to delete cable (and lose history) |
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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide. |
Giving this one a little bump. Who wants to take a run at it? |
This would be very helpful. One of our team members spent a whole day entering cable terminations in the wrong direction, and being able to edit this instead of starting over would be fantastic. |
NetBox version
v3.5.6
Feature type
Change to existing functionality
Proposed functionality
Currently, if someone accidentally connects a cable to the rear port instead of the front port, the entire cable must be deleted and created again. It would be nice to be able to change not only the port number but also the location (front/rear) when editing the cable. This might just be an ui change as the api seems to allow to change it.
Use case
It is not necessary to delete the cable and enter all information (label, length etc) again. You can just reconnect it.
Database changes
No response
External dependencies
No response
The text was updated successfully, but these errors were encountered: