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

Column VLAN Tagged VLANs as summary. #8850

New Issue
Closed
opened 2025-12-29 20:42:02 +01:00 by adam · 11 comments
adam commented 2025-12-29 20:42:02 +01:00
Owner
Copy Link

Originally created by @LHBL2003 on GitHub (Nov 16, 2023).

NetBox version

v.3.6.5

Feature type

Change to existing functionality

Proposed functionality

We have around 100 tagged VLANs on some ports, e.g. 2000-2100 for development systems.

The Tagged VLANs column can be displayed in the interface overview. The only problem is that the view then explodes.

It would be good to have a Short Tagged VLANs column, where only the numbers are listed as a summary. As is the case with some switch manufacturers, for example. So e.g. VLAN: 1;5;10;2000-2100

Before
image

Afterwards
image

Use case

The overview in the list view for the interfaces is retained. If 30 ports with VLAN 2000 to 2100 are tagged on a 48 port switch, you lose the overview. The Short VLANs column would maintain clarity despite the large amount of information.

Database changes

No response

External dependencies

No response

Originally created by @LHBL2003 on GitHub (Nov 16, 2023). ### NetBox version v.3.6.5 ### Feature type Change to existing functionality ### Proposed functionality We have around 100 tagged VLANs on some ports, e.g. 2000-2100 for development systems. The Tagged VLANs column can be displayed in the interface overview. The only problem is that the view then explodes. It would be good to have a Short Tagged VLANs column, where only the numbers are listed as a summary. As is the case with some switch manufacturers, for example. So e.g. VLAN: 1;5;10;2000-2100 Before ![image](https://github.com/netbox-community/netbox/assets/46369917/ad63282a-45b5-4cd3-8acd-72a28a7b7261) Afterwards ![image](https://github.com/netbox-community/netbox/assets/46369917/5e25bb99-93f1-409c-9d25-5bfd661bdc76) ### Use case The overview in the list view for the interfaces is retained. If 30 ports with VLAN 2000 to 2100 are tagged on a 48 port switch, you lose the overview. The Short VLANs column would maintain clarity despite the large amount of information. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closurecomplexity: medium labels 2025-12-29 20:42:02 +01:00
adam closed this issue 2025-12-29 20:42:03 +01:00
adam commented 2025-12-29 20:42:03 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Nov 16, 2023):

How do you propose to linkfy the items? Or is the intent to not have a way to link the items at all?

@abhi1693 commented on GitHub (Nov 16, 2023): How do you propose to linkfy the items? Or is the intent to not have a way to link the items at all?
adam commented 2025-12-29 20:42:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 16, 2023):

One option would be to list only n items, and if the total count exceeds n display a link to the filtered list view in addition to the objects listed.

@jeremystretch commented on GitHub (Nov 16, 2023): One option would be to list only _n_ items, and if the total count exceeds _n_ display a link to the filtered list view in addition to the objects listed.
adam commented 2025-12-29 20:42:04 +01:00
Author
Owner
Copy Link

@LHBL2003 commented on GitHub (Nov 16, 2023):

@jeremystretch

I also like your solution very much. Anything is better than having to scroll 2 screens for an interface. :)

@LHBL2003 commented on GitHub (Nov 16, 2023): @jeremystretch I also like your solution very much. Anything is better than having to scroll 2 screens for an interface. :)
adam commented 2025-12-29 20:42:04 +01:00
Author
Owner
Copy Link

@dejantep commented on GitHub (Nov 22, 2023):

One option would be to list only n items, and if the total count exceeds n display a link to the filtered list view in addition to the objects listed.

Or maybe even just a count of VLANS as an integer. The view is pretty jammed with info and imho it would be good to keep it as clean as possible

@dejantep commented on GitHub (Nov 22, 2023): > One option would be to list only _n_ items, and if the total count exceeds _n_ display a link to the filtered list view in addition to the objects listed. Or maybe even just a count of VLANS as an integer. The view is pretty jammed with info and imho it would be good to keep it as clean as possible
adam commented 2025-12-29 20:42:04 +01:00
Author
Owner
Copy Link

@LHBL2003 commented on GitHub (Nov 23, 2023):

@dejantep: This would then correspond to the picture above.
Personally, I like both ideas better than the current situation.

@LHBL2003 commented on GitHub (Nov 23, 2023): @dejantep: This would then correspond to the picture above. Personally, I like both ideas better than the current situation.
adam commented 2025-12-29 20:42:04 +01:00
Author
Owner
Copy Link

@LHBL2003 commented on GitHub (Nov 28, 2023):

@jeremystretch
Could you accept a variant as a suggestion for improvement, I don't care which one, the main thing is that the overview improves.
Thank you

@LHBL2003 commented on GitHub (Nov 28, 2023): @jeremystretch Could you accept a variant as a suggestion for improvement, I don't care which one, the main thing is that the overview improves. Thank you
adam commented 2025-12-29 20:42:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 28, 2023):

Please stop pinging me. I will spend time on this issue when I am able.

@jeremystretch commented on GitHub (Nov 28, 2023): Please stop pinging me. I will spend time on this issue when I am able.
adam commented 2025-12-29 20:42:05 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 27, 2024):

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 (Feb 27, 2024): 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:42:05 +01:00
Author
Owner
Copy Link

@LHBL2003 commented on GitHub (Mar 26, 2024):

The current situation is that if I have set the tagged VLAN 2000 to 2100 on a switch port, I now only document the first and last VLAN in Netbox. Because the current form of the table display obscures my view. It doesn't have to be that the current column display is replaced. Perhaps it is possible to offer further column displays.

Idea (Very short)
If there were another column display, then this would certainly be the best choice. Because it is short and crisp.
By clicking on the link you can then access a filtered VLAN list for this interface.

Example representation:
image

Idea (Short but very informative)
However, I don't think Jeremystretch's variant is bad either, which limits the list to e.g. 3 to 10 items and everything else is accessed via e.g. 3 points.

image

So that you don't have to click so much, you can hover over the 3 points and get a tooltip where more is displayed in advance.

image
<a title="Test 0 (2000)&#013;Test 1 (2001)" href="/ipam/vlans/32/">...</a>

I won't be able to realise it. I don't have the experience to debug everything properly. But I have tried whether the tooltip can be solved via Google Chrome :) In combination with Jeremystretch's train of thought, this second idea could be really good.

@LHBL2003 commented on GitHub (Mar 26, 2024): The current situation is that if I have set the tagged VLAN 2000 to 2100 on a switch port, I now only document the first and last VLAN in Netbox. Because the current form of the table display obscures my view. It doesn't have to be that the current column display is replaced. Perhaps it is possible to offer further column displays. **Idea (Very short)** If there were another column display, then this would certainly be the best choice. Because it is short and crisp. By clicking on the link you can then access a filtered VLAN list for this interface. Example representation: ![image](https://github.com/netbox-community/netbox/assets/46369917/fcdc0a73-99b8-4898-9452-db22b0ee0bb3) **Idea (Short but very informative)** However, I don't think Jeremystretch's variant is bad either, which limits the list to e.g. 3 to 10 items and everything else is accessed via e.g. 3 points. ![image](https://github.com/netbox-community/netbox/assets/46369917/9dca3ee5-f0af-4fc3-a543-552ee16b8650) So that you don't have to click so much, you can hover over the 3 points and get a tooltip where more is displayed in advance. ![image](https://github.com/netbox-community/netbox/assets/46369917/6eb3aa01-7034-4322-b4b5-f030ded20b42) `<a title="Test 0 (2000)&#013;Test 1 (2001)" href="/ipam/vlans/32/">...</a>` I won't be able to realise it. I don't have the experience to debug everything properly. But I have tried whether the tooltip can be solved via Google Chrome :) In combination with Jeremystretch's train of thought, this second idea could be really good.
adam commented 2025-12-29 20:42:05 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 22, 2024):

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 (Aug 22, 2024): 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:42:05 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 21, 2024):

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 (Sep 21, 2024): 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: medium 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#8850
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?