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

Interface - Tagged VLAN - Multiselect (Selection of 100 consecutive VLANS) #9390

New Issue
Closed
opened 2025-12-29 20:49:13 +01:00 by adam · 8 comments
adam commented 2025-12-29 20:49:13 +01:00
Owner
Copy Link

Originally created by @LHBL2003 on GitHub (Mar 26, 2024).

NetBox version

v3.7.4

Feature type

Change to existing functionality

Proposed functionality

There is an interface for one device. Several tagged VLANs can be assigned to each interface. However, you must click on each VLAN individually. (Example path: https://netbox/dcim/interfaces/xxxx/edit/?return_url=/dcim/devices/xxx/interfaces/)

Function extension proposal:

There is an "open selector" Function in the "IPAM --> Edit prefix" area, perhaps you can use this function here. (Only with multiselector function.)

  • The X button is used to delete the entire content.
  • The "open Selector" button is used for multiple selection and adds further VLANs to the "Tagged VLANs" field.

image

  • I think a very good solution that can be useful in many areas is to have checkboxes. (See picture below) Either you tick what you need.
  • Or if you filter well, then you can select everything via "Check All" and add it to the existing selection.

(This will certainly work even better than with the current DropDown field. Because every time the DropDown list gets bigger, the selection area also jumps a little).

image

For example:
There is an open selector in the "Editing prefix" area.

Use case

Much faster documentation of large VLAN numbers.

The reason why, after much deliberation, I would like to have this function after all:

In the previous post, the behaviour when selecting VLANs in the device interface configuration was improved. (Because every time the drop-down list gets bigger, the selection area also jumps a little.). https://github.com/netbox-community/netbox/issues/9307

Unfortunately, it is still very tedious to click on 100 VLANs. We have more and more locations where we set up a lot of consecutive VLAN IDs. It's super easy in a switch and super time-consuming in Netbox.

For the feeling

HP Switch:

config t
interface 10 tagged vlan 2000-2100
save

Finish

Netbox Tagged VLANs Dropdown List:

2000 ... Click
2001 ... Click
2002 ... Click
2003 ... Click
A long moment later.
2100 ... Click

The result is that you no longer document correctly in Netbox. In the meantime, you only click on the first and last VLAN in the series in Netbox, e.g. 2000 and 2100. The VLANs 2001 to 2099 are not assigned to the interface. However, they are all configured in the switch. It is therefore important to realise that only partial documentation is carried out here.

It would therefore be very, very, very nice if you could somehow click on all consecutive VLANs at the same time.

Database changes

I would say no, as the operation of the front end is customised.

External dependencies

Unknown

Originally created by @LHBL2003 on GitHub (Mar 26, 2024). ### NetBox version v3.7.4 ### Feature type Change to existing functionality ### Proposed functionality There is an interface for one device. Several tagged VLANs can be assigned to each interface. However, you must click on each VLAN individually. (Example path: https://netbox/dcim/interfaces/xxxx/edit/?return_url=/dcim/devices/xxx/interfaces/) **Function extension proposal:** There is an "open selector" Function in the "IPAM --> Edit prefix" area, perhaps you can use this function here. (Only with multiselector function.) - The X button is used to delete the entire content. - The "open Selector" button is used for multiple selection and adds further VLANs to the "Tagged VLANs" field. ![image](https://github.com/netbox-community/netbox/assets/46369917/2ec03f4c-a61c-4ac6-864b-e8babe4fe615) - I think a very good solution that can be useful in many areas is to have checkboxes. (See picture below) Either you tick what you need. - Or if you filter well, then you can select everything via "Check All" and add it to the existing selection. (This will certainly work even better than with the current DropDown field. Because every time the DropDown list gets bigger, the selection area also jumps a little). ![image](https://github.com/netbox-community/netbox/assets/46369917/9a388f3e-4c96-45ad-8241-9af9926d188a) **For example:** There is an open selector in the "Editing prefix" area. ### Use case Much faster documentation of large VLAN numbers. ### The reason why, after much deliberation, I would like to have this function after all: In the previous post, the behaviour when selecting VLANs in the device interface configuration was improved. (Because every time the drop-down list gets bigger, the selection area also jumps a little.). https://github.com/netbox-community/netbox/issues/9307 Unfortunately, it is still very tedious to click on 100 VLANs. We have more and more locations where we set up a lot of consecutive VLAN IDs. It's super easy in a switch and super time-consuming in Netbox. **For the feeling** ---------------------------------------------------------------------- **HP Switch:** ``` config t interface 10 tagged vlan 2000-2100 save ``` Finish ---------------------------------------------------------------------- **Netbox Tagged VLANs Dropdown List:** 2000 ... Click 2001 ... Click 2002 ... Click 2003 ... Click A long moment later. 2100 ... Click ---------------------------------------------------------------------- The result is that you no longer document correctly in Netbox. In the meantime, you only click on the first and last VLAN in the series in Netbox, e.g. 2000 and 2100. The VLANs 2001 to 2099 are not assigned to the interface. However, they are all configured in the switch. It is therefore important to realise that only partial documentation is carried out here. It would therefore be very, very, very nice if you could somehow click on all consecutive VLANs at the same time. ### Database changes I would say no, as the operation of the front end is customised. ### External dependencies Unknown
adam added the type: featurestatus: needs ownerpending closurecomplexity: high labels 2025-12-29 20:49:13 +01:00
adam closed this issue 2025-12-29 20:49:13 +01:00
adam commented 2025-12-29 20:49:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 26, 2024):

Allow the selection of several Tagged VLANs simultaneously in the interface.

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (Mar 26, 2024): > Allow the selection of several Tagged VLANs simultaneously in the interface. Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 20:49:14 +01:00
Author
Owner
Copy Link

@LHBL2003 commented on GitHub (Mar 26, 2024):

Sorry I hope that fits better?

@LHBL2003 commented on GitHub (Mar 26, 2024): Sorry I hope that fits better?
adam commented 2025-12-29 20:49:14 +01:00
Author
Owner
Copy Link

@LHBL2003 commented on GitHub (Mar 26, 2024):

Especially in combination with these topics, it should be a strong further development for netbox on the topic of many VLANS.

Column VLAN Tagged VLANs as summary.
https://github.com/netbox-community/netbox/issues/14285

Interface VLAN group (Memory last filter)
https://github.com/netbox-community/netbox/issues/15273

@LHBL2003 commented on GitHub (Mar 26, 2024): Especially in combination with these topics, it should be a strong further development for netbox on the topic of many VLANS. Column VLAN Tagged VLANs as summary. https://github.com/netbox-community/netbox/issues/14285 Interface VLAN group (Memory last filter) https://github.com/netbox-community/netbox/issues/15273
adam commented 2025-12-29 20:49:14 +01:00
Author
Owner
Copy Link

@LHBL2003 commented on GitHub (Apr 5, 2024):

Hi jeremystretch, (and I'm not tagging you as requested ;)

I think I have found a very, very, very good solution with the "Open Selector". And I hope you like it just as much. Even if I found the relatively new "Open Selector" function rather impractical at some point. But here the function would fit 1000% and really do a good job.

@LHBL2003 commented on GitHub (Apr 5, 2024): Hi jeremystretch, (and I'm not tagging you as requested ;) I think I have found a very, very, very good solution with the "Open Selector". And I hope you like it just as much. Even if I found the relatively new "Open Selector" function rather impractical at some point. But here the function would fit 1000% and really do a good job.
adam commented 2025-12-29 20:49:15 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 20, 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 (Aug 20, 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).
adam commented 2025-12-29 20:49:15 +01:00
Author
Owner
Copy Link

@jdavidson2021 commented on GitHub (Sep 6, 2024):

VLAN assignments in NetBox are still our biggest complaint with the tool. Making it easier to assign VLANs to an interface in the UI would be helpful, but our preference would be to assign the list of vlans to an interface during the interface csv import process. Similar to the this open issue request: #14171

@jdavidson2021 commented on GitHub (Sep 6, 2024): VLAN assignments in NetBox are still our biggest complaint with the tool. Making it easier to assign VLANs to an interface in the UI would be helpful, but our preference would be to assign the list of vlans to an interface during the interface csv import process. Similar to the this open issue request: #14171
adam commented 2025-12-29 20:49:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 6, 2024):

@jdavidson2021 would you like to volunteer to implement this FR?

@jeremystretch commented on GitHub (Sep 6, 2024): @jdavidson2021 would you like to volunteer to implement this FR?
adam commented 2025-12-29 20:49:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 10, 2024):

Closing this out as there have been no volunteers.

@jeremystretch commented on GitHub (Oct 10, 2024): Closing this out as there have been no volunteers.
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: high pending closure status: needs owner 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#9390
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?