Skip to content
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

Closed
jweiher opened this issue Jul 27, 2023 · 4 comments · Fixed by #16049
Closed

Cables/UI: Unable to change from front to rear while editing cable #13278

jweiher opened this issue Jul 27, 2023 · 4 comments · Fixed by #16049
Labels
status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation topic: cabling type: feature Introduction of new functionality to the application

Comments

@jweiher
Copy link

jweiher commented Jul 27, 2023

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

@jweiher jweiher added the type: feature Introduction of new functionality to the application label Jul 27, 2023
@atolgac
Copy link

atolgac commented Jul 28, 2023

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)

@jeremystretch jeremystretch added the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Oct 13, 2023
Copy link
Contributor

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.

@github-actions github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Jan 12, 2024
@jeffgdotorg jeffgdotorg removed the pending closure Requires immediate attention to avoid being closed for inactivity label Jan 24, 2024
@jeffgdotorg
Copy link
Contributor

Giving this one a little bump. Who wants to take a run at it?

@eronlloyd
Copy link

eronlloyd commented Jan 26, 2024

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation topic: cabling type: feature Introduction of new functionality to the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants