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 a Table in the VRF view that shows all the Interfaces in that VRF #11511

New Issue
Closed
opened 2025-12-29 21:46:13 +01:00 by adam · 4 comments
adam commented 2025-12-29 21:46:13 +01:00
Owner
Copy Link

Originally created by @AaronJamesMyers on GitHub (Aug 21, 2025).

NetBox version

v4.1.10

Feature type

Other

Proposed functionality

Add a Table into the VRF objects view that shows all the interfaces that are members of that VRF, so you can view them all quickly without having to search through all the interfaces.

This is something that I added in a template extension in a plugin I developed, but i think this is something that lots of ISP's(or anyone using VRF's really) would find useful.

Use case

Anytime your looking for all the members of a VRF to view a network segment, you need to filter interfaces by which VRF's they are in. But having something in the VRF view that displays that by default would be a much quicker way to get that info, and it should be a pretty easy thing to implement.

Database changes

No response

External dependencies

No response

Originally created by @AaronJamesMyers on GitHub (Aug 21, 2025). ### NetBox version v4.1.10 ### Feature type Other ### Proposed functionality Add a Table into the VRF objects view that shows all the interfaces that are members of that VRF, so you can view them all quickly without having to search through all the interfaces. This is something that I added in a template extension in a plugin I developed, but i think this is something that lots of ISP's(or anyone using VRF's really) would find useful. ### Use case Anytime your looking for all the members of a VRF to view a network segment, you need to filter interfaces by which VRF's they are in. But having something in the VRF view that displays that by default would be a much quicker way to get that info, and it should be a pretty easy thing to implement. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:46:13 +01:00
adam closed this issue 2025-12-29 21:46:13 +01:00
adam commented 2025-12-29 21:46:13 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Aug 21, 2025):

Potentially related to #18147.

@jnovinger commented on GitHub (Aug 21, 2025): Potentially related to #18147.
adam commented 2025-12-29 21:46:14 +01:00
Author
Owner
Copy Link

@AaronJamesMyers commented on GitHub (Aug 21, 2025):

definitely asking for the same thing. Either solution works, (an interfaces category in the "related objects" table, or a completely seperate table for interfaces.

@AaronJamesMyers commented on GitHub (Aug 21, 2025): definitely asking for the same thing. Either solution works, (an interfaces category in the "related objects" table, or a completely seperate table for interfaces.
adam commented 2025-12-29 21:46:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 21, 2025):

We generally try to avoid embedding tables of related objects under detail views except where there's a very strong hierarchical relationship, to avoid cluttering the UI. I've reopened FR #18147 as an alternative to this proposal.

@jeremystretch commented on GitHub (Aug 21, 2025): We generally try to avoid embedding tables of related objects under detail views except where there's a very strong hierarchical relationship, to avoid cluttering the UI. I've reopened FR #18147 as an alternative to this proposal.
adam commented 2025-12-29 21:46:14 +01:00
Author
Owner
Copy Link

@AaronJamesMyers commented on GitHub (Aug 21, 2025):

I understand, we have some VRF's with >50 interfaces, and the table is kind of dominating the view now.

@AaronJamesMyers commented on GitHub (Aug 21, 2025): I understand, we have some VRF's with >50 interfaces, and the table is kind of dominating the view now.
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 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#11511
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?