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

Include circuit terminations when importing new circuits #639

New Issue
Closed
opened 2025-12-29 16:24:09 +01:00 by adam · 4 comments
adam commented 2025-12-29 16:24:09 +01:00
Owner
Copy Link

Originally created by @patrickfish on GitHub (Jan 19, 2017).

Originally assigned to: @jeremystretch on GitHub.

When adding or editing a circuit, there is no longer a field for Site. Previous to ~1.8.2 you could select the Site that the circuit was associated with.

I do see that I can edit the terminations of the circuit once it's created, but we don't always have a termination point when adding the circuit for the first time.

Is this intended behavior or a bug?

Originally created by @patrickfish on GitHub (Jan 19, 2017). Originally assigned to: @jeremystretch on GitHub. When adding or editing a circuit, there is no longer a field for Site. Previous to ~1.8.2 you could select the Site that the circuit was associated with. I do see that I can edit the terminations of the circuit once it's created, but we don't always have a termination point when adding the circuit for the first time. Is this intended behavior or a bug?
adam added the status: acceptedtype: feature labels 2025-12-29 16:24:09 +01:00
adam closed this issue 2025-12-29 16:24:10 +01:00
adam commented 2025-12-29 16:24:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 19, 2017):

v1.8.0 introduced the concept of circuit terminations, of which each circuit can have up to two. You'll need to first create the desired circuit, and then add terminations (either to a site or to a specific device within that site) separately.

I realize this isn't the most intuitive workflow. It may be workable to combine the creation of a circuit and its first termination in the same form, but I haven't yet looked into it.

@jeremystretch commented on GitHub (Jan 19, 2017): v1.8.0 introduced the concept of circuit terminations, of which each circuit can have up to two. You'll need to first create the desired circuit, and then add terminations (either to a site or to a specific device within that site) separately. I realize this isn't the most intuitive workflow. It may be workable to combine the creation of a circuit and its first termination in the same form, but I haven't yet looked into it.
adam commented 2025-12-29 16:24:10 +01:00
Author
Owner
Copy Link

@patrickfish commented on GitHub (Jan 19, 2017):

Ok - that makes sense from what I'm seeing then.

I add circuits as we get the turn-up information from the carrier, which is often before active equipment arrives. It's would be nice to have it tied to a specific site at this point.

Same goes for importing circuits as I see Site is no longer a field there. If I import 100 circuits, they're now somewhat orphaned because I have no other metadata that tells me what site it belongs to. Other circuits don't ever get a termination (ie broadband circuit to a SOHO router) but we still want to have a list of circuits per site.

@patrickfish commented on GitHub (Jan 19, 2017): Ok - that makes sense from what I'm seeing then. I add circuits as we get the turn-up information from the carrier, which is often before active equipment arrives. It's would be nice to have it tied to a specific site at this point. Same goes for importing circuits as I see Site is no longer a field there. If I import 100 circuits, they're now somewhat orphaned because I have no other metadata that tells me what site it belongs to. Other circuits don't ever get a termination (ie broadband circuit to a SOHO router) but we still want to have a list of circuits per site.
adam commented 2025-12-29 16:24:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 24, 2020):

This is going to be fairly difficult to implement given the current model for circuit terminations, but it's up for grabs if anyone wants to dig into it.

@jeremystretch commented on GitHub (Jul 24, 2020): This is going to be fairly difficult to implement given the current model for circuit terminations, but it's up for grabs if anyone wants to dig into it.
adam commented 2025-12-29 16:24:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 14, 2020):

This is almost certainly going to be much easier to accomplish once #4347 has added JSON/YAML-based import for all objects. Marking this as blocked pending that work.

@jeremystretch commented on GitHub (Aug 14, 2020): This is almost certainly going to be much easier to accomplish once #4347 has added JSON/YAML-based import for all objects. Marking this as blocked pending that work.
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: accepted 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#639
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?