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

Display LAG in logical order #6419

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

Originally created by @snowie-swe on GitHub (Apr 28, 2022).

NetBox version

v3.2.2

Feature type

Change to existing functionality

Proposed functionality

I would like to change the way that LAG ports are views in the UI.
Currently the interfaces are "tagged" with LAG port number, but its hard to visualize in the GUI on devices with large number of interface.

Use case

Currently LAG are represented the following way.

image

Proposed change:
Reorder interface in the list when they are added to an LAG to be represented as "childs"
This would make it easier within UI to visualize what ports are included in an LAG.

image

Database changes

dont know

External dependencies

dont know

Originally created by @snowie-swe on GitHub (Apr 28, 2022). ### NetBox version v3.2.2 ### Feature type Change to existing functionality ### Proposed functionality I would like to change the way that LAG ports are views in the UI. Currently the interfaces are "tagged" with LAG port number, but its hard to visualize in the GUI on devices with large number of interface. ### Use case Currently LAG are represented the following way. ![image](https://user-images.githubusercontent.com/41901413/165830241-79a53be5-0d31-4c33-8a00-1db804498f83.png) Proposed change: Reorder interface in the list when they are added to an LAG to be represented as "childs" This would make it easier within UI to visualize what ports are included in an LAG. ![image](https://user-images.githubusercontent.com/41901413/165830568-fcfcb825-d01b-45c8-ae0e-d533439b2a87.png) ### Database changes dont know ### External dependencies dont know
adam added the type: feature label 2025-12-29 19:40:30 +01:00
adam closed this issue 2025-12-29 19:40:30 +01:00
adam commented 2025-12-29 19:40:30 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 29, 2022):

This seems like a poor design choice IMO. Imagine trying to find a specific physical interface in a list of dozens or hundreds of others, only to find it missing. It might not even occur to the user to scroll down and check under LAG interfaces, and even if it does, you wouldn't know which LAG to check.

@jeremystretch commented on GitHub (Apr 29, 2022): This seems like a poor design choice IMO. Imagine trying to find a specific physical interface in a list of dozens or hundreds of others, only to find it missing. It might not even occur to the user to scroll down and check under LAG interfaces, and even if it does, you wouldn't know which LAG to check.
adam commented 2025-12-29 19:40:30 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 11, 2022):

I'm going to close this as the proposed change would be highly undesirable for many users as noted above.

@jeremystretch commented on GitHub (May 11, 2022): I'm going to close this as the proposed change would be highly undesirable for many users as noted above.
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#6419
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?