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

Wrong circuit counting in the Site view Related Objects card #7319

New Issue
Closed
opened 2025-12-29 20:21:42 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:21:42 +01:00
Owner
Copy Link

Originally created by @renatoalmeidaoliveira on GitHub (Dec 3, 2022).

Originally assigned to: @renatoalmeidaoliveira on GitHub.

NetBox version

v3.3.9

Python version

3.10

Steps to Reproduce

  1. Create a Site
  2. Create a Circuit
  3. Put both termination in the created Site

Expected Behavior

The site view should show only one Circuit in the Related Objects card

Observed Behavior

The site view should shows two Circuit in the Related Objects card

Originally created by @renatoalmeidaoliveira on GitHub (Dec 3, 2022). Originally assigned to: @renatoalmeidaoliveira on GitHub. ### NetBox version v3.3.9 ### Python version 3.10 ### Steps to Reproduce 1. Create a Site 2. Create a Circuit 3. Put both termination in the created Site ### Expected Behavior The site view should show only one Circuit in the Related Objects card ### Observed Behavior The site view should shows two Circuit in the Related Objects card
adam added the type: bugstatus: accepted labels 2025-12-29 20:21:42 +01:00
adam closed this issue 2025-12-29 20:21:42 +01:00
adam commented 2025-12-29 20:21:43 +01:00
Author
Owner
Copy Link

@renatoalmeidaoliveira commented on GitHub (Dec 3, 2022):

For this issue I can think in two possible solutions:

Change the text in the Site template from "Circuit" to "Circuit Terminations";
Change the Site view to count only circuits

@renatoalmeidaoliveira commented on GitHub (Dec 3, 2022): For this issue I can think in two possible solutions: Change the text in the Site template from "Circuit" to "Circuit Terminations"; Change the Site view to count only circuits
adam commented 2025-12-29 20:21:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 6, 2022):

I think your approach in #11116 is the right way to go. 👍

@jeremystretch commented on GitHub (Dec 6, 2022): I think your approach in #11116 is the right way to go. :+1:
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: bug
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#7319
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?