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

Add optional Site field to WirelessLAN model #7139

New Issue
Closed
opened 2025-12-29 20:19:39 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:19:39 +01:00
Owner
Copy Link

Originally created by @tyler-8 on GitHub (Oct 20, 2022).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.3.5

Feature type

Data model extension

Proposed functionality

Add an optional ForeignKey field pointing to Site for the WirelessLAN model.

Also show the Site relation in the various GUI components where applicable: WirelessLAN detail & list views (as column and filter), the Site detail page "Related Objects" table, etc.

Use case

With more than a few SSIDs in NetBox it can be a challenge to identify where exactly a WLAN resides without digging into the related VLAN information, or the related interface/device attachments.

Additionally, given that VLAN<->site membership is optional, and a WLAN may be documented without physical interface relationships, it creates more possible confusion. Having the Site relationship be clearly & directly established with the WirelessLAN would improve the documentation capabilities vastly.

Database changes

New ForeignKey field on WirelessLAN model

External dependencies

N/A

Originally created by @tyler-8 on GitHub (Oct 20, 2022). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.3.5 ### Feature type Data model extension ### Proposed functionality Add an optional `ForeignKey` field pointing to `Site` for the `WirelessLAN` model. Also show the `Site` relation in the various GUI components where applicable: WirelessLAN detail & list views (as column and filter), the Site detail page "Related Objects" table, etc. ### Use case With more than a few SSIDs in NetBox it can be a challenge to identify where exactly a WLAN resides without digging into the related VLAN information, or the related interface/device attachments. Additionally, given that VLAN<->site membership is optional, and a WLAN may be documented without physical interface relationships, it creates more possible confusion. Having the Site relationship be clearly & directly established with the WirelessLAN would improve the documentation capabilities vastly. ### Database changes New ForeignKey field on WirelessLAN model ### External dependencies N/A
adam added the status: acceptedtype: featurenetboxcomplexity: low labels 2025-12-29 20:19:39 +01:00
adam closed this issue 2025-12-29 20:19:39 +01:00
adam commented 2025-12-29 20:19:40 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 25, 2022):

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 (Dec 25, 2022): 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.
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 netbox 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#7139
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?