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

Include device and site in overlay terminations list view #6745

New Issue
Closed
opened 2025-12-29 19:44:55 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:44:55 +01:00
Owner
Copy Link

Originally created by @dejantep on GitHub (Jul 30, 2022).

Originally assigned to: @DanSheps on GitHub.

NetBox version

v3.3-beta

Feature type

Change to existing functionality

Proposed functionality

When looking at the details of certain l2vpn you can see list of terminations. Columns included are "object type" and "Assigned object". It would be much better if you could also include columns device and site. Also add these fields under "filters" section. That would make it possible to quickly find terminations on device or site.
This would improve usability imho.

Use case

My guess is that this is just matter of displaying whats already there.

Database changes

none

External dependencies

none

Originally created by @dejantep on GitHub (Jul 30, 2022). Originally assigned to: @DanSheps on GitHub. ### NetBox version v3.3-beta ### Feature type Change to existing functionality ### Proposed functionality When looking at the details of certain l2vpn you can see list of terminations. Columns included are "object type" and "Assigned object". It would be much better if you could also include columns device and site. Also add these fields under "filters" section. That would make it possible to quickly find terminations on device or site. This would improve usability imho. ### Use case My guess is that this is just matter of displaying whats already there. ### Database changes none ### External dependencies none
adam added the status: acceptedtype: featurebeta labels 2025-12-29 19:44:55 +01:00
adam closed this issue 2025-12-29 19:44:55 +01:00
adam commented 2025-12-29 19:44:55 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Aug 2, 2022):

The difficulty with this one is that some terminations can be vlans or vm interfaces, which don't nessicarily have a corresponding "parent" in every case.

@DanSheps commented on GitHub (Aug 2, 2022): The difficulty with this one is that some terminations can be vlans or vm interfaces, which don't nessicarily have a corresponding "parent" in every case.
adam commented 2025-12-29 19:44:56 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Aug 2, 2022):

I think I have a workable solution.

@DanSheps commented on GitHub (Aug 2, 2022): I think I have a workable solution.
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 beta 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#6745
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?