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

Bulk editing interfaces clears the tagged VLAN list #8864

New Issue
Closed
opened 2025-12-29 20:42:17 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:42:17 +01:00
Owner
Copy Link

Originally created by @dpotter-intoto on GitHub (Nov 21, 2023).

NetBox version

v3.5.3

Python version

3.8

Steps to Reproduce

  1. In a list of interfaces, select the checkbox near a number of interfaces, some of which are in 802.1Q "Tagged" mode and have a list of 802.1q tagged VLANs
  2. Click "Edit"
  3. Change any property of the interface (e.g. description, tags). Do NOT click "Set to null" next to the "Tagged VLANs' field.
  4. Click "Apply"
  5. Observe that the interfaces are still in tagged mode, but no longer have a list of VLANs

Expected Behavior

Unless the "Tagged VLANs" "set to null" checkbox is selected, the field should not be cleared.

Observed Behavior

The "Tagged VLANs" field was cleared

Originally created by @dpotter-intoto on GitHub (Nov 21, 2023). ### NetBox version v3.5.3 ### Python version 3.8 ### Steps to Reproduce 1. In a list of interfaces, select the checkbox near a number of interfaces, some of which are in 802.1Q "Tagged" mode and have a list of 802.1q tagged VLANs 2. Click "Edit" 3. Change any property of the interface (e.g. description, tags). Do NOT click "Set to null" next to the "Tagged VLANs' field. 4. Click "Apply" 5. Observe that the interfaces are still in tagged mode, but no longer have a list of VLANs ### Expected Behavior Unless the "Tagged VLANs" "set to null" checkbox is selected, the field should not be cleared. ### Observed Behavior The "Tagged VLANs" field was cleared
adam added the type: bugstatus: duplicate labels 2025-12-29 20:42:17 +01:00
adam closed this issue 2025-12-29 20:42:18 +01:00
adam commented 2025-12-29 20:42:18 +01:00
Author
Owner
Copy Link

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

It looks like you've run into bug #12983, which was resolved in NetBox v3.5.5. Please upgrade to this or a later release to resolve the issue.

@jeremystretch commented on GitHub (Nov 22, 2023): It looks like you've run into bug #12983, which was resolved in NetBox v3.5.5. Please upgrade to this or a later release to resolve the issue.
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 status: duplicate type: bug
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#8864
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?