starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Provide Interface and Label for VLAN table view as done in Device Interface view #7108

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

Originally created by @jcralbino on GitHub (Oct 14, 2022).

NetBox version

v3.3.5

Feature type

Change to existing functionality

Proposed functionality

Currently when seeing the VLAN attached device interfaces we only see the associated lag interface name , without its label name

Check Current usage where for lag name: <Interface_name>
image

Proposed: Improve UX by providing this <Interface_name>(<label_name>) as seen in the device view where lag interface is represented also with its label :

image

Test Procedure using demo environment.

  1. In demo

  2. Attach a vlan in Po1 of device dmi01-yonkers-sw01

  3. Add a label to Po1 (Label_Po1) of device

  4. Check the resulting table when going to the VLAN

  5. Check the resulting table when going to the Device Interface view

Use case

Improve the UI visibility and better UX

Database changes

none

External dependencies

none

Originally created by @jcralbino on GitHub (Oct 14, 2022). ### NetBox version v3.3.5 ### Feature type Change to existing functionality ### Proposed functionality Currently when seeing the VLAN attached device interfaces we only see the associated lag interface name , without its label name Check Current usage where for lag name: <Interface_name> ![image](https://user-images.githubusercontent.com/44149262/195841750-b0163c26-b0d6-4fba-a243-abc52957db87.png) Proposed: Improve UX by providing this <Interface_name>(<label_name>) as seen in the device view where lag interface is represented also with its label : ![image](https://user-images.githubusercontent.com/44149262/195841623-320211d0-b467-48e4-9126-8bea0c33cf41.png) Test Procedure using demo environment. 1. In [demo](https://demo.netbox.dev) 2. Attach a vlan in Po1 of device [dmi01-yonkers-sw01](https://demo.netbox.dev/dcim/devices/26/) 3. Add a label to Po1 (Label_Po1) of device 4. Check the resulting table when going to the VLAN 5. Check the resulting table when going to the Device Interface view ### Use case Improve the UI visibility and better UX ### Database changes none ### External dependencies none
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 20:19:21 +01:00
adam closed this issue 2025-12-29 20:19:21 +01:00
adam commented 2025-12-29 20:19:22 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 18, 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 (Dec 18, 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 20:19:22 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 17, 2023):

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 (Jan 17, 2023): 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 status: needs owner 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#7108
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?