Add "Wireless LAN Group" and "Wireless LANs" to Bulk Edit and to Interface Bulk Import pages +Make Nullable #7303

Closed
opened 2025-12-29 20:21:33 +01:00 by adam · 2 comments
Owner

Originally created by @cyberndj on GitHub (Dec 1, 2022).

NetBox version

v3.3.9

Feature type

Data model extension

Proposed functionality

Adding the fields "Wireless LAN Group" and "Wireless LANs" to the Bulk Edit page would let a user mass edit Wireless kind interfaces to be updated with the correct info. Also adding ability to make the "Wireless LANs" field NULLable to clear out the values would be beneficial to some.

Also adding the same two fields to the Bulk Import page for interfaces can also aid those who want to bulk import interfaces with the Wireless LANs already.

Use case

The current way to add "Wireless LANs" to a wireless interface is to edit each interface page with the values. Adding the fields to the bulk edit page would allow users to filter select multiple interfaces and bulk update them in one action. (These two fields are currently missing in the bulk edit page)

Having the ability to NULL the field would also help clear values.

Adding the fields to the interface import page would allow users to add "Wireless LANs" to interface for bulk additions. (The Wireless LANs field is currently missing in imports)

A work flow could be:

  1. Import new APs using a .csv with a device type that has a wireless interface.
  2. Bulk edit based on a filter to update the APs interface with the correct "Wireless LANs" using the Wireless LAN Group field to narrow down the list.

Database changes

I'm guessing none.

External dependencies

None

Originally created by @cyberndj on GitHub (Dec 1, 2022). ### NetBox version v3.3.9 ### Feature type Data model extension ### Proposed functionality Adding the fields "Wireless LAN Group" and "Wireless LANs" to the Bulk Edit page would let a user mass edit Wireless kind interfaces to be updated with the correct info. Also adding ability to make the "Wireless LANs" field NULLable to clear out the values would be beneficial to some. Also adding the same two fields to the Bulk Import page for interfaces can also aid those who want to bulk import interfaces with the Wireless LANs already. ### Use case The current way to add "Wireless LANs" to a wireless interface is to edit each interface page with the values. Adding the fields to the bulk edit page would allow users to filter select multiple interfaces and bulk update them in one action. (These two fields are currently missing in the bulk edit page) Having the ability to NULL the field would also help clear values. Adding the fields to the interface import page would allow users to add "Wireless LANs" to interface for bulk additions. (The Wireless LANs field is currently missing in imports) A work flow could be: 1. Import new APs using a .csv with a device type that has a wireless interface. 2. Bulk edit based on a filter to update the APs interface with the correct "Wireless LANs" using the Wireless LAN Group field to narrow down the list. ### Database changes I'm guessing none. ### External dependencies None
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 20:21:33 +01:00
adam closed this issue 2025-12-29 20:21:33 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Apr 6, 2023):

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 (Apr 6, 2023): 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

@github-actions[bot] commented on GitHub (May 6, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (May 6, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7303