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

Changing VLAN group scope type does not toggle selection fields correctly #5227

New Issue
Closed
opened 2025-12-29 19:25:40 +01:00 by adam · 0 comments
adam commented 2025-12-29 19:25:40 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Aug 25, 2021).

NetBox version

v3.0-beta2

Python version

3.7

Steps to Reproduce

  1. Navigate to IPAM > VLAN Groups > Add
  2. Select several different scope types and observe the selection fields below

Expected Behavior

Initially, none of the selection fields below scope type should be present. Once a scope type has been selected, only the relevant selection fields should be displayed.

For example, if the scope type has been set to "site," only the region, site group, and site fields should be visible.

Observed Behavior

Initially, all scope selection fields are visible instead of hidden. After selecting a scope type, the form widgets are hidden, however the parent form "rows" (with labels) are not.

Originally created by @jeremystretch on GitHub (Aug 25, 2021). ### NetBox version v3.0-beta2 ### Python version 3.7 ### Steps to Reproduce 1. Navigate to IPAM > VLAN Groups > Add 2. Select several different scope types and observe the selection fields below ### Expected Behavior Initially, none of the selection fields below scope type should be present. Once a scope type has been selected, only the relevant selection fields should be displayed. For example, if the scope type has been set to "site," only the region, site group, and site fields should be visible. ### Observed Behavior Initially, all scope selection fields are visible instead of hidden. After selecting a scope type, the form widgets are hidden, however the parent form "rows" (with labels) are not.
adam added the type: bugbeta labels 2025-12-29 19:25:40 +01:00
adam closed this issue 2025-12-29 19:25:40 +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 beta 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#5227
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?