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

Provide a single "scope" field for bulk editing VLAN group scope assignments #10375

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

Originally created by @jeremystretch on GitHub (Oct 16, 2024).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.1.4

Feature type

Change to existing functionality

Triage priority

I volunteer to perform this work (if approved)

Proposed functionality

Bulk editing the scope assignment of VLAN groups currently employs a barrage of individual fields, which makes for a confusing user experience. We should replace these with a single scope field, filtered by a type selector, as we have in the edit form for an individual VLAN group:

screenshot

Use case

This will greatly simplify the UX for bulk editing VLAN group scope assignments.

Database changes

N/A

External dependencies

N/A

Originally created by @jeremystretch on GitHub (Oct 16, 2024). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.1.4 ### Feature type Change to existing functionality ### Triage priority I volunteer to perform this work (if approved) ### Proposed functionality Bulk editing the scope assignment of VLAN groups currently employs a barrage of individual fields, which makes for a confusing user experience. We should replace these with a single `scope` field, filtered by a type selector, as we have in the edit form for an individual VLAN group: ![screenshot](https://github.com/user-attachments/assets/8584f9b6-7ee1-4942-9c15-b8f8baff7db5) ### Use case This will greatly simplify the UX for bulk editing VLAN group scope assignments. ### Database changes N/A ### External dependencies N/A
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:30:37 +01:00
adam closed this issue 2025-12-29 21:30:38 +01:00
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: low status: accepted 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#10375
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?