Automatically clear dependent selection fields when modifying a parent selection #8824

Closed
opened 2025-12-29 20:41:44 +01:00 by adam · 3 comments
Owner

Originally created by @jeremystretch on GitHub (Nov 9, 2023).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.6.4

Feature type

Change to existing functionality

Proposed functionality

When selecting a different option of a selection field, any dependent selection fields should be reset. For example, when editing a device which currently assigned to a site and location, changing the value of the site field in the form should clear the value of the location field.

Use case

This will avoid user confusion by making it clear that the previously populated selection in the dependent field is no longer valid and a new selection must be made (where applicable).

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Nov 9, 2023). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.6.4 ### Feature type Change to existing functionality ### Proposed functionality When selecting a different option of a selection field, any dependent selection fields should be reset. For example, when editing a device which currently assigned to a site and location, changing the value of the site field in the form should clear the value of the location field. ### Use case This will avoid user confusion by making it clear that the previously populated selection in the dependent field is no longer valid and a new selection must be made (where applicable). ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 20:41:44 +01:00
adam closed this issue 2025-12-29 20:41:45 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 8, 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 (Feb 8, 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).
Author
Owner

@jeremystretch commented on GitHub (Feb 8, 2024):

Now that #14917 is wrapping up, this is something we should revisit in v4.0.

@jeremystretch commented on GitHub (Feb 8, 2024): Now that #14917 is wrapping up, this is something we should revisit in v4.0.
Author
Owner

@jeremystretch commented on GitHub (Feb 8, 2024):

This ended up being a trivial change, so I've bundled it with #14917 in PR #15080.

@jeremystretch commented on GitHub (Feb 8, 2024): This ended up being a trivial change, so I've bundled it with #14917 in PR #15080.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8824