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

Cable Identifier #2271

Closed
siddallhotmail opened this issue Jul 25, 2018 · 2 comments
Closed

Cable Identifier #2271

siddallhotmail opened this issue Jul 25, 2018 · 2 comments
Labels
status: duplicate This issue has already been raised

Comments

@siddallhotmail
Copy link

[X ] Feature request
[ ] Bug report
[ ] Documentation
[ ] Housekeeping

Hi I'd like to request a new feature which would allow us to identify cables within the Netbox system.

In our datacentres all cables are labelled with a unique cable ID, so that when patching equipment in an engineer can ascertain what cables are in use and where.

I'd like a new field to be added to the dcim_interfaceconnections table as "cable_id" which is a unique field and would allow us to populate a cable ID when making a connection between two interfaces.

I've already made the changes in a fork of the main code... but would prefer to keep with the NetBox official release.

Many thanks

Martin

@siddallhotmail
Copy link
Author

Can see this is similar to #20 but that doesn't seem to be making any progress, been open since 2016 !!

@lampwins
Copy link
Contributor

@martinpsiddall this sort of thing is best served under #20. You will find there has been quite a lot of activity on that issue lately. You can also find that it has been tagged for v2.5. Yes, #20 is currently the oldest FR, but it is also by far one of the most complex to implement, so great care must be taken in its design.

@jeremystretch jeremystretch added the status: duplicate This issue has already been raised label Jul 25, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jan 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: duplicate This issue has already been raised
Projects
None yet
Development

No branches or pull requests

3 participants