Skip to content

Add field 'Location' to the 'CircuitTermination' model #11721

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

Closed
PieterL75 opened this issue Feb 10, 2023 · 5 comments
Closed

Add field 'Location' to the 'CircuitTermination' model #11721

PieterL75 opened this issue Feb 10, 2023 · 5 comments
Labels
status: duplicate This issue has already been raised type: feature Introduction of new functionality to the application

Comments

@PieterL75
Copy link
Contributor

NetBox version

3.4.4

Feature type

Data model extension

Proposed functionality

When creating a 'Termination' in a Circuit, the highest detail for a 'Site' is 'Site.
I would like to see this extended with 'Location' and made it optional

Gui updates :
https://demo.netbox.dev/circuits/circuits/19/
Extend the 'Site' row with the location (if choosen)
image

https://demo.netbox.dev/circuits/circuit-terminations/23/edit/?return_url=/circuits/circuits/19/
In the 'Site' part, add a dropdown for 'Location'
image

https://demo.netbox.dev/circuits/circuits/
Add the location to the 'Side A/Z' column view, or add a new columns 'Location A, Location B'
(I prefer the first)
image

Use case

We have crossconnects that run between 2 buildings in one Location. Currently, these are stored as 'SiteA <-> SiteA'
With this added field, it can be differentiated as 'SiteA/Building1 <-> SiteA/Bullding2'

Database changes

Add a new field 'Location' to the 'CircuitTermination' model

External dependencies

No response

@PieterL75 PieterL75 added the type: feature Introduction of new functionality to the application label Feb 10, 2023
@jsenecal jsenecal changed the title Add 'Site' to Circuit Termination Add field 'Location' to the 'CircuitTermination' model Feb 16, 2023
@jeremystretch jeremystretch added the status: under review Further discussion is needed to determine this issue's scope and/or implementation label May 3, 2023
@gjvc
Copy link

gjvc commented Jul 8, 2023

We have cross-connects that run between two cages (Location) in the same facility (Site)

For netbox 2.5 I proposed this when Location was known as a "Rack Group". For netbox 3.2 I proposed this to add Location to a circuit termination.

I'd be happy to create a PR for netbox 3.4 and/or 3.5 as appropriate.

@KPTheProf
Copy link

We have multiple sites where we have circuits terminating in different buildings, I think that this would be a useful update to be able to track the correct locations. We have a major WAN project starting where this would be of benefit to us. Do you have any idea of timescale as to when / if this will be implemented please?

@netbox-community netbox-community deleted a comment from GoldyXXD Aug 18, 2023
@netbox-community netbox-community deleted a comment from jwbensley Aug 18, 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 Nov 17, 2023
@jeremystretch jeremystretch added needs milestone Awaiting prioritization for inclusion with a future NetBox release and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation pending closure Requires immediate attention to avoid being closed for inactivity labels Dec 5, 2023
@jeremystretch jeremystretch added status: backlog Awaiting selection for work complexity: high Expected to require a large amont of time and effort to implement relative to other tasks labels May 21, 2024
@jeffgdotorg
Copy link
Contributor

Flagging facial similarity between this issue and #9604

@jeremystretch
Copy link
Member

Duplicate of #9604

@jeremystretch jeremystretch marked this as a duplicate of #9604 Sep 25, 2024
@jeremystretch jeremystretch closed this as not planned Won't fix, can't repro, duplicate, stale Sep 25, 2024
@jeremystretch jeremystretch added status: duplicate This issue has already been raised and removed needs milestone Awaiting prioritization for inclusion with a future NetBox release status: backlog Awaiting selection for work complexity: high Expected to require a large amont of time and effort to implement relative to other tasks labels Sep 25, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 25, 2024
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 type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

5 participants