Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add optional Site field to WirelessLAN model #10711

Closed
tyler-8 opened this issue Oct 20, 2022 · 1 comment
Closed

Add optional Site field to WirelessLAN model #10711

tyler-8 opened this issue Oct 20, 2022 · 1 comment
Assignees
Labels
complexity: low Requires minimal effort to implement netbox status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@tyler-8
Copy link
Contributor

tyler-8 commented Oct 20, 2022

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

@tyler-8 tyler-8 added the type: feature Introduction of new functionality to the application label Oct 20, 2022
@jeremystretch jeremystretch added the status: under review Further discussion is needed to determine this issue's scope and/or implementation label Oct 25, 2022
@github-actions
Copy link
Contributor

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 github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Dec 25, 2022
@jeremystretch jeremystretch added needs milestone Awaiting prioritization for inclusion with a future NetBox release and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation pending closure Requires immediate attention to avoid being closed for inactivity labels Jan 5, 2023
@jeremystretch jeremystretch added the status: backlog Awaiting selection for work label May 21, 2024
@arthanson arthanson added the complexity: low Requires minimal effort to implement label May 22, 2024
@jeffgdotorg jeffgdotorg added this to the v4.1 milestone May 31, 2024
@jeffgdotorg jeffgdotorg removed the needs milestone Awaiting prioritization for inclusion with a future NetBox release label Jun 7, 2024
@arthanson arthanson assigned arthanson and unassigned arthanson Jul 9, 2024
@jeremystretch jeremystretch removed this from the v4.1 milestone Jul 12, 2024
@jeffgdotorg jeffgdotorg added the needs milestone Awaiting prioritization for inclusion with a future NetBox release label Jul 14, 2024
@jeremystretch jeremystretch added this to the v4.2 milestone Sep 26, 2024
@jeremystretch jeremystretch removed the needs milestone Awaiting prioritization for inclusion with a future NetBox release label Sep 26, 2024
@jeremystretch jeremystretch added v4.2 and removed v4.2 labels Oct 18, 2024
@jeremystretch jeremystretch added the netbox label Nov 1, 2024 — with Linear
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: backlog Awaiting selection for work labels Nov 1, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 6, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
complexity: low Requires minimal effort to implement netbox status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

4 participants