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

Device Interface "VLAN group" Filter deletes “Untagged VLAN” and “Tagged VLANs” entry. "Netbox Version V4" #10304

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

Originally created by @LHBL2003 on GitHub (Sep 30, 2024).

Deployment Type

Self-hosted

NetBox Version

v4.1.2

Python Version

3.10

Steps to Reproduce

Since some sub-versions of version 4, the settings of “Untagged VLAN” and “Tagged VLANs” are deleted as soon as “VLAN group” is selected again for a device interface.

I thought I had already reported this, but unfortunately not.

  1. create 2 VLAN groups (VLAN Group A, VLAN Group B) with 2 VLANs each (Test A.1, Test A.2, Test B.1, Test B.2).
  2. open a device interface.
  3. 802.1Q Switching:
    • 802.1Q Mode = Tagged
    • VLAN group = VLAN Group A
    • Untagged VLAN = Test A.1 (1234)
    • Tagged VLANs = Test A.1 (1234)
  4. change “VLAN group” to “VLAN Group B”

Result, “Untagged VLAN” and “Tagged VLANs” are emptied.

2024-09-30_09h13_50

Jeremy's statement years ago was that “VLAN group” is only a filter to be able to search better in “Untagged VLAN” “Tagged VLANs”. This is also the reason why “VLAN group” is not saved.

The fact that “VLAN group” now empties the entries “Untagged VLAN” and “Tagged VLANs” is not good.

Expected Behavior

“Untagged VLAN” and ‘Tagged VLANs’ remain unchanged when ‘VLAN group’ is changed.

Observed Behavior

VLAN group” empties ‘Untagged VLAN’ and ‘Tagged VLANs’.

Originally created by @LHBL2003 on GitHub (Sep 30, 2024). ### Deployment Type Self-hosted ### NetBox Version v4.1.2 ### Python Version 3.10 ### Steps to Reproduce Since some sub-versions of version 4, the settings of “Untagged VLAN” and “Tagged VLANs” are deleted as soon as “VLAN group” is selected again for a device interface. I thought I had already reported this, but unfortunately not. 1. create 2 VLAN groups (VLAN Group A, VLAN Group B) with 2 VLANs each (Test A.1, Test A.2, Test B.1, Test B.2). 2. open a device interface. 3. 802.1Q Switching: - 802.1Q Mode = Tagged - VLAN group = VLAN Group A - Untagged VLAN = Test A.1 (1234) - Tagged VLANs = Test A.1 (1234) 4. change “VLAN group” to “VLAN Group B” Result, “Untagged VLAN” and “Tagged VLANs” are emptied. ![2024-09-30_09h13_50](https://github.com/user-attachments/assets/66cd05e4-8303-468d-aabc-48a299bb2529) Jeremy's statement years ago was that “VLAN group” is only a filter to be able to search better in “Untagged VLAN” “Tagged VLANs”. This is also the reason why “VLAN group” is not saved. The fact that “VLAN group” now empties the entries “Untagged VLAN” and “Tagged VLANs” is not good. ### Expected Behavior “Untagged VLAN” and ‘Tagged VLANs’ remain unchanged when ‘VLAN group’ is changed. ### Observed Behavior VLAN group” empties ‘Untagged VLAN’ and ‘Tagged VLANs’.
adam closed this issue 2025-12-29 21:29:39 +01:00
adam commented 2025-12-29 21:29:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 30, 2024):

This is working as intended. Selecting a new VLAN group obviously invalidates any selections made under a previous group.

@jeremystretch commented on GitHub (Sep 30, 2024): This is working as intended. Selecting a new VLAN group obviously invalidates any selections made under a previous group.
adam commented 2025-12-29 21:29:40 +01:00
Author
Owner
Copy Link

@LHBL2003 commented on GitHub (Sep 30, 2024):

@jeremystretch: That you don't want to be tagged with your name. But sorry, the ticket was closed too quickly. With an unacceptable reason.

But that was never the case in version 3.
What sense does that make?
Why is it being done differently now? Netbox V3 to V4?

Now it works worse than ever before. I understood that the group name is not saved. But someone must have decided that the other fields are suddenly cleared as soon as the group filter is used.

We know that many locations often have the same VLAN name. That's why we have given the VLAN groups a location abbreviation. But now we also have several topics at one location, and we may also need a VLAN from another group, which in turn has names that exist at other locations.

If I want to clear the entries for Tagged and Untaged, I can press X. That's better than what the system does now. Especially if someone doesn't realise that all TAGs are deleted just because they want to add 10 more.

@LHBL2003 commented on GitHub (Sep 30, 2024): @jeremystretch: That you don't want to be tagged with your name. But sorry, the ticket was closed too quickly. With an unacceptable reason. But that was never the case in version 3. What sense does that make? Why is it being done differently now? Netbox V3 to V4? Now it works worse than ever before. I understood that the group name is not saved. But someone must have decided that the other fields are suddenly cleared as soon as the group filter is used. We know that many locations often have the same VLAN name. That's why we have given the VLAN groups a location abbreviation. But now we also have several topics at one location, and we may also need a VLAN from another group, which in turn has names that exist at other locations. If I want to clear the entries for Tagged and Untaged, I can press X. That's better than what the system does now. Especially if someone doesn't realise that all TAGs are deleted just because they want to add 10 more.
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
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#10304
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?