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

Nested interfaces table (grouping) #5212

New Issue
Closed
opened 2025-12-29 19:25:30 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:25:30 +01:00
Owner
Copy Link

Originally created by @hiddenman on GitHub (Aug 20, 2021).

NetBox version

3.0-beta2

Feature type

Change to existing functionality

Proposed functionality

I'd like to propose a new way of displaying interfaces with nesting/grouping.

For example, we have hundreds of interfaces like:
physical interfaces -> LAG interface -> Virtual interfaces.

Currently Netbox displays all interfaces without any nesting and it's very hard to find out what is linked, where and how.
Of course we can do a little bit of sorting but that doesn't help much.

Here is an example of how it looks on the real hardware:

image

So maybe adding of some grouping options would be useful for all.

This (closed) issue might be relevant as well: https://github.com/netbox-community/netbox/issues/373

Use case

In case of hundreds of physical links, tens of LAG interfaces and hundreds of virtual interfaces on top the them it's very hard to track grouping/nesting and levels of abstractions.

Database changes

No response

External dependencies

No response

Originally created by @hiddenman on GitHub (Aug 20, 2021). ### NetBox version 3.0-beta2 ### Feature type Change to existing functionality ### Proposed functionality I'd like to propose a new way of displaying interfaces with nesting/grouping. For example, we have hundreds of interfaces like: physical interfaces -> LAG interface -> Virtual interfaces. Currently Netbox displays all interfaces without any nesting and it's very hard to find out what is linked, where and how. Of course we can do a little bit of sorting but that doesn't help much. Here is an example of how it looks on the real hardware: ![image](https://user-images.githubusercontent.com/4009515/130260198-f92fe872-8bf7-4add-907f-b6d8cf6dd033.png) So maybe adding of some grouping options would be useful for all. This (closed) issue might be relevant as well: https://github.com/netbox-community/netbox/issues/373 ### Use case In case of hundreds of physical links, tens of LAG interfaces and hundreds of virtual interfaces on top the them it's very hard to track grouping/nesting and levels of abstractions. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:25:30 +01:00
adam closed this issue 2025-12-29 19:25:30 +01:00
adam commented 2025-12-29 19:25:30 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 23, 2021):

I'm not sure this would work out as cleanly as you're expecting. Maybe you'd like to try mocking something up using the NetBox UI?

@jeremystretch commented on GitHub (Aug 23, 2021): I'm not sure this would work out as cleanly as you're expecting. Maybe you'd like to try mocking something up using the NetBox UI?
adam commented 2025-12-29 19:25:30 +01:00
Author
Owner
Copy Link

@hiddenman commented on GitHub (Aug 23, 2021):

I'm not sure this would work out as cleanly as you're expecting. Maybe you'd like to try mocking something up using the NetBox UI?

Thank you.

  1. Do you mean just prepare an image with some examples?
  2. As other guys said in Slack, it would be better to just add a Grouping columns feature, similar to Select columns. So a user would be able to group interfaces in his own way. For example, 2-3 levels of groups. Is it technically possible in the current UI framework?
@hiddenman commented on GitHub (Aug 23, 2021): > I'm not sure this would work out as cleanly as you're expecting. Maybe you'd like to try mocking something up using the NetBox UI? Thank you. 1. Do you mean just prepare an image with some examples? 2. As other guys said in Slack, it would be better to just add a Grouping columns feature, similar to Select columns. So a user would be able to group interfaces in his own way. For example, 2-3 levels of groups. Is it technically possible in the current UI framework?
adam commented 2025-12-29 19:25:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 23, 2021):

  1. Do you mean just prepare an image with some examples?

I mean dig into the way the table is generated in NetBox, and actually manipulate the code to render the proposed layout. A screenshot just isn't sufficient for a proposed change this complex. It doesn't have to be pull request quality, but it does need to be functional to the point that you can write up a detailed implementation proposal.

  1. As other guys said in Slack, it would be better to just add a Grouping columns feature, similar to Select columns. So a user would be able to group interfaces in his own way. For example, 2-3 levels of groups. Is it technically possible in the current UI framework?

I doubt this would be feasible, but that's another reason to dig into the code.

@jeremystretch commented on GitHub (Aug 23, 2021): > 1. Do you mean just prepare an image with some examples? I mean dig into the way the table is generated in NetBox, and actually manipulate the code to render the proposed layout. A screenshot just isn't sufficient for a proposed change this complex. It doesn't have to be pull request quality, but it does need to be functional to the point that you can write up a detailed implementation proposal. > 2. As other guys said in Slack, it would be better to just add a Grouping columns feature, similar to Select columns. So a user would be able to group interfaces in his own way. For example, 2-3 levels of groups. Is it technically possible in the current UI framework? I doubt this would be feasible, but that's another reason to dig into the code.
adam commented 2025-12-29 19:25:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 5, 2021):

@hiddenman have you made any progress on this?

@jeremystretch commented on GitHub (Oct 5, 2021): @hiddenman have you made any progress on this?
adam commented 2025-12-29 19:25:31 +01:00
Author
Owner
Copy Link

@hiddenman commented on GitHub (Oct 5, 2021):

@hiddenman have you made any progress on this?

Unfortunately, not yet. We were thinking about moving to Netbox and finally decided to do this. So i hope in the nearest future i will be able to think about it.
If you want to close it then go ahead. Will reopen when i'm ready.

@hiddenman commented on GitHub (Oct 5, 2021): > @hiddenman have you made any progress on this? Unfortunately, not yet. We were thinking about moving to Netbox and finally decided to do this. So i hope in the nearest future i will be able to think about it. If you want to close it then go ahead. Will reopen when i'm ready.
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#5212
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?