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

Sort and group related interfaces in Device Interface tab #6729

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

Originally created by @jahknem on GitHub (Jul 27, 2022).

NetBox version

v3.2.7

Feature type

Change to existing functionality

Proposed functionality

I'd like to have the possibility to have all child interfaces grouped beneath the parent interfaces. These should be indented beneath their respective parent interface like this:

parent
> child
> child
> > grandchild
> child

The same functionality can be found in the prefix view, where child prefixes are grouped beneath their parent interfaces and indented as per their child status.

As interfaces can be related with other interfaces in a bridge or lag relationship, this is how I would propose the view for lag and bridge relationships:
A similar functionality for bridges:

|-toBeBridged1
|-toBeBridged2
|-toBeBridged3

and lag groups:

----------
| phy1
| phy2
----------

would also be useful.

Use case

Currently when an interface is classified as a child interface of another interface, the relationship is only visible when changing the table settings to show parent interfaces. If one wants to see the child interfaces of an interface, the Interface menu has to be opened.
While this is fine if the child interfaces have the same name stem as the parent interface, in a situation where this is not the case and there is a large number of interfaces (e.g. the ont interfaces of a (g)pon interface), it is difficult to search all child interfaces of a parent interface.
A grouping of these interfaces beneath their parent interface would enable a more efficient workflow.

Database changes

No response

External dependencies

No response

Originally created by @jahknem on GitHub (Jul 27, 2022). ### NetBox version v3.2.7 ### Feature type Change to existing functionality ### Proposed functionality I'd like to have the possibility to have all child interfaces grouped beneath the parent interfaces. These should be indented beneath their respective parent interface like this: ``` parent > child > child > > grandchild > child ``` The same functionality can be found in the prefix view, where child prefixes are grouped beneath their parent interfaces and indented as per their child status. As interfaces can be related with other interfaces in a bridge or lag relationship, this is how I would propose the view for lag and bridge relationships: A similar functionality for bridges: ``` |-toBeBridged1 |-toBeBridged2 |-toBeBridged3 ``` and lag groups: ``` ---------- | phy1 | phy2 ---------- ``` would also be useful. ### Use case Currently when an interface is classified as a child interface of another interface, the relationship is only visible when changing the table settings to show parent interfaces. If one wants to see the child interfaces of an interface, the Interface menu has to be opened. While this is fine if the child interfaces have the same name stem as the parent interface, in a situation where this is not the case and there is a large number of interfaces (e.g. the ont interfaces of a (g)pon interface), it is difficult to search all child interfaces of a parent interface. A grouping of these interfaces beneath their parent interface would enable a more efficient workflow. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 19:44:33 +01:00
adam closed this issue 2025-12-29 19:44:34 +01:00
adam commented 2025-12-29 19:44:34 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 26, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Sep 26, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:44:34 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 27, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Oct 27, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure 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#6729
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?