starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

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

New Issue
Closed
opened 2025-12-29 20:26:13 +01:00 by adam · 5 comments
adam commented 2025-12-29 20:26:13 +01:00
Owner
Copy Link

Originally created by @PieterL75 on GitHub (Feb 10, 2023).

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

Originally created by @PieterL75 on GitHub (Feb 10, 2023). ### 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://user-images.githubusercontent.com/74899468/218033491-45c8db7b-725e-4083-95d9-c750a0b1c9fc.png) 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://user-images.githubusercontent.com/74899468/218033625-13ade254-e140-4a32-9098-89714d1fd7f0.png) 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](https://user-images.githubusercontent.com/74899468/218033709-2068756f-d1a0-4991-bc39-cb54ea0a7dc6.png) ### 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_
adam added the type: featurestatus: duplicate labels 2025-12-29 20:26:13 +01:00
adam closed this issue 2025-12-29 20:26:13 +01:00
adam commented 2025-12-29 20:26:13 +01:00
Author
Owner
Copy Link

@gjvc commented on GitHub (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.

@gjvc commented on GitHub (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](https://github.com/netbox-community/netbox/issues/2929) when Location was known as a "Rack Group". For netbox 3.2 I proposed [this](https://github.com/netbox-community/netbox/issues/9604) 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.
adam commented 2025-12-29 20:26:13 +01:00
Author
Owner
Copy Link

@KPTheProf commented on GitHub (Jul 20, 2023):

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?

@KPTheProf commented on GitHub (Jul 20, 2023): 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?
adam commented 2025-12-29 20:26:14 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 17, 2023):

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[bot] commented on GitHub (Nov 17, 2023): 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](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:26:14 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Jul 14, 2024):

Flagging facial similarity between this issue and #9604

@jeffgdotorg commented on GitHub (Jul 14, 2024): Flagging facial similarity between this issue and #9604
adam commented 2025-12-29 20:26:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 25, 2024):

Duplicate of #9604

@jeremystretch commented on GitHub (Sep 25, 2024): Duplicate of #9604
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: duplicate type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7628
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?