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

Please implement moving ends of a cable #4881

Closed
ThomasGiger opened this issue Jul 22, 2020 · 10 comments
Closed

Please implement moving ends of a cable #4881

ThomasGiger opened this issue Jul 22, 2020 · 10 comments
Labels
pending closure Requires immediate attention to avoid being closed for inactivity status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: feature Introduction of new functionality to the application

Comments

@ThomasGiger
Copy link

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.

@jeremystretch jeremystretch added status: blocked Another issue or external requirement is preventing implementation type: feature Introduction of new functionality to the application labels Jul 24, 2020
@jeremystretch
Copy link
Member

Blocked by #4900

@raddessi
Copy link

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

@jeremystretch jeremystretch added status: under review Further discussion is needed to determine this issue's scope and/or implementation and removed status: blocked Another issue or external requirement is preventing implementation labels Mar 29, 2021
@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation labels Apr 13, 2021
@jeremystretch
Copy link
Member

Open for volunteers under v2.11.

@github-actions
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. Please see our contributing guide.

@github-actions github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Jun 13, 2021
@eronlloyd
Copy link

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

@hellerve
Copy link
Contributor

hellerve commented 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.

@jeremystretch
Copy link
Member

@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 jeremystretch added status: accepted This issue has been accepted for implementation and removed pending closure Requires immediate attention to avoid being closed for inactivity status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Aug 4, 2021
@hellerve
Copy link
Contributor

hellerve commented 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!

@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed status: accepted This issue has been accepted for implementation labels Oct 26, 2021
@github-actions
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. Please see our contributing guide.

@github-actions github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Dec 25, 2021
@netbox-community netbox-community deleted a comment from Nothing4You Dec 26, 2021
@github-actions
Copy link
Contributor

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 github-actions bot locked as resolved and limited conversation to collaborators Apr 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
pending closure Requires immediate attention to avoid being closed for inactivity status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants