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

Additional column for compact tagged vlan view in device interface list #10344

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

Originally created by @jakobsen-lrz on GitHub (Oct 10, 2024).

NetBox version

v4.1.1

Feature type

Other

Triage priority

I volunteer to perform this work (if approved)

Proposed functionality

Hello,

for my current workplace the tagged VLAN list, as seen in device interfaces, is too unwieldy, as we sometimes have a few hundred tagged vlans on a single interface. Also the newly added change that the vlan list is external, if it is more than three, would be very impractical for our use case.

I propose to add an optional column to the device interface list, that only shows the vlan IDs, and not the full name, and with more than one VLAN per line. I implemented this already myself, and created a patchfile. After i applied the patchfile on my personal netbox instance, it seemed worked without problems. I will also be testing it on our v4.1.1 test instance of netbox. "Tagged Vlans (Compact)" is the name i gave to this extra column.

It would also be acceptable for us, if there was an official mechanism to alter the formatting for the vlan list.

Thanks

Use case

Allows for better visibility of tagged vlans on device interfaces, while still allowing quick searching using Ctrl+F.

Database changes

Should be none, i changed the BaseInterfaceTable in ./netbox/dcim/tables/devices.py, and added the new columns name to the column lists. I think this doesnt alter the database, as i didnt alter any models.

External dependencies

None

Originally created by @jakobsen-lrz on GitHub (Oct 10, 2024). ### NetBox version v4.1.1 ### Feature type Other ### Triage priority I volunteer to perform this work (if approved) ### Proposed functionality Hello, for my current workplace the tagged VLAN list, as seen in device interfaces, is too unwieldy, as we sometimes have a few hundred tagged vlans on a single interface. Also the newly added change that the vlan list is external, if it is more than three, would be very impractical for our use case. I propose to add an optional column to the device interface list, that only shows the vlan IDs, and not the full name, and with more than one VLAN per line. I implemented this already myself, and created a patchfile. After i applied the patchfile on my personal netbox instance, it seemed worked without problems. I will also be testing it on our v4.1.1 test instance of netbox. `"Tagged Vlans (Compact)"` is the name i gave to this extra column. It would also be acceptable for us, if there was an official mechanism to alter the formatting for the vlan list. Thanks ### Use case Allows for better visibility of tagged vlans on device interfaces, while still allowing quick searching using Ctrl+F. ### Database changes Should be none, i changed the BaseInterfaceTable in `./netbox/dcim/tables/devices.py`, and added the new columns name to the column lists. I think this doesnt alter the database, as i didnt alter any models. ### External dependencies None
adam closed this issue 2025-12-29 21:30:17 +01:00
adam commented 2025-12-29 21:30:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 6, 2025):

I propose to add an optional column to the device interface list, that only shows the vlan IDs, and not the full name, and with more than one VLAN per line.

IMO that probably wouldn't be very useful as it would be practically illegible (just a wrapping list of numbers).

Maybe just showing the count of VLANs assigned to the interface would make more sense?

@jeremystretch commented on GitHub (Feb 6, 2025): > I propose to add an optional column to the device interface list, that only shows the vlan IDs, and not the full name, and with more than one VLAN per line. IMO that probably wouldn't be very useful as it would be practically illegible (just a wrapping list of numbers). Maybe just showing the count of VLANs assigned to the interface would make more sense?
adam commented 2025-12-29 21:30:18 +01:00
Author
Owner
Copy Link

@jakobsen-lrz commented on GitHub (Feb 7, 2025):

I understand. For our usage there is sadly no alternative, and showing a count of assigned VLANs is sadly also not helpful.

Currently we have a netbox instance where i have changed the templates to achieve this. Would adding a feature to be able change formatting of some things via configuration.py be a possibility? Like having an option to define how VLANs are formatted?

@jakobsen-lrz commented on GitHub (Feb 7, 2025): I understand. For our usage there is sadly no alternative, and showing a count of assigned VLANs is sadly also not helpful. Currently we have a netbox instance where i have changed the templates to achieve this. Would adding a feature to be able change formatting of some things via configuration.py be a possibility? Like having an option to define how VLANs are formatted?
adam commented 2025-12-29 21:30:19 +01:00
Author
Owner
Copy Link

@cybarox commented on GitHub (Feb 14, 2025):

I did some testing. My idea is to display the VLANs with their VIDs as badges like tags (see screenshot). It would be a plus if it were possible to assign colors to the prefix/VLAN roles like with the device roles, so that the badges with the VLAN VIDs could be shown in the role's color; otherwise, a default color would be used when no role or color for a role is defined.

Image

@cybarox commented on GitHub (Feb 14, 2025): I did some testing. My idea is to display the VLANs with their VIDs as badges like tags (see screenshot). It would be a plus if it were possible to assign colors to the prefix/VLAN roles like with the device roles, so that the badges with the VLAN VIDs could be shown in the role's color; otherwise, a default color would be used when no role or color for a role is defined. ![Image](https://github.com/user-attachments/assets/8652536f-7899-41a4-83ce-9f5ee46e2c24)
adam commented 2025-12-29 21:30:19 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 16, 2025):

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 (May 16, 2025): 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/main/CONTRIBUTING.md).
adam commented 2025-12-29 21:30:19 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 15, 2025):

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 (Jun 15, 2025): 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 complexity: low netbox 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#10344
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?