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

Create new workflow for interface VLAN assignment #1607

New Issue
Closed
opened 2025-12-29 16:33:26 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:33:26 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Mar 6, 2018).

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: 2.3.1

Description

Device interfaces can be assigned one or more VLANs. Currently, this is accomplished using a multi-widget hierarchy to select VLANs by their site and/or VLAN group. We should be able to compress these into a single dropdown which presents all available VLANs grouped as such:

  • Global VLANs
  • Site VLANs (no group)
  • Each VLAN group within the site

This will simplify VLAN assignment, especially during bulk editing.

Originally created by @jeremystretch on GitHub (Mar 6, 2018). ### Issue type [x] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> ### Environment * Python version: 3.5.2 * NetBox version: 2.3.1 ### Description Device interfaces can be assigned one or more VLANs. Currently, this is accomplished using a multi-widget hierarchy to select VLANs by their site and/or VLAN group. We should be able to compress these into a single dropdown which presents all available VLANs grouped as such: * Global VLANs * Site VLANs (no group) * Each VLAN group within the site This will simplify VLAN assignment, especially during bulk editing.
adam added the status: acceptedtype: housekeeping labels 2025-12-29 16:33:26 +01:00
adam closed this issue 2025-12-29 16:33:26 +01:00
adam commented 2025-12-29 16:33:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 8, 2018):

I started out merely wanting to create a more convenient field for interface VLAN assignments, but that proved to be insufficient, so I overhauled the workflow and added a VLANs table to the interface edit view. Existing VLAN assignments are shown and modified in this table; new VLANs can be assigned via a separate view.

I had to remove the bulk edit ability for now, as the current implementation is limited (a user cannot assign VLANs from different groups) and dangerous (assigning VLANs via bulk edit will wipe out any existing assignments).

@jeremystretch commented on GitHub (Mar 8, 2018): I started out merely wanting to create a more convenient field for interface VLAN assignments, but that proved to be insufficient, so I overhauled the workflow and added a VLANs table to the interface edit view. Existing VLAN assignments are shown and modified in this table; new VLANs can be assigned via a separate view. I had to remove the bulk edit ability for now, as the current implementation is limited (a user cannot assign VLANs from different groups) and dangerous (assigning VLANs via bulk edit will wipe out any existing assignments).
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: accepted type: housekeeping
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#1607
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?