Allow bulk assignment/unassignment of VLANs to interfaces #9284

Closed
opened 2025-12-29 20:47:50 +01:00 by adam · 1 comment
Owner

Originally created by @elipsion on GitHub (Feb 23, 2024).

Originally assigned to: @bctiemann on GitHub.

NetBox version

v3.7.0

Feature type

Change to existing functionality

Proposed functionality

When bulk editing interfaces, I would like to be able to add and remove assignment of tagged VLANs, rather than explicitly setting the list of VLANs.

This would make VLAN editing more in line with the tagging workflow.

Use case

Adding a VLAN to a large number of ports (in my case adding a VLAN to several hundred hypervisor uplink interfaces) it would be preferable to not have to list the existing VLAN assignments when adding a new one.

Database changes

None

External dependencies

None

Originally created by @elipsion on GitHub (Feb 23, 2024). Originally assigned to: @bctiemann on GitHub. ### NetBox version v3.7.0 ### Feature type Change to existing functionality ### Proposed functionality When bulk editing interfaces, I would like to be able to _add_ and _remove_ assignment of tagged VLANs, rather than explicitly _setting_ the list of VLANs. This would make VLAN editing more in line with the tagging workflow. ### Use case Adding a VLAN to a large number of ports (in my case adding a VLAN to several hundred hypervisor uplink interfaces) it would be preferable to not have to list the existing VLAN assignments when adding a new one. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: featurenetboxcomplexity: low labels 2025-12-29 20:47:50 +01:00
adam closed this issue 2025-12-29 20:47:50 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Aug 21, 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 21, 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).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9284