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 VLAN group (Memory last filter) --> New Ideea: Replace VLAN group #9294

New Issue
Closed
opened 2025-12-29 20:47:56 +01:00 by adam · 5 comments
adam commented 2025-12-29 20:47:56 +01:00
Owner
Copy Link

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

NetBox version

v3.7.1

Feature type

Change to existing functionality
The original idea behind this feature request was to save the VLAN group filter field. Due to a revised proposal on the subject of tagged VLANs (https://github.com/netbox-community/netbox/issues/15530), my opinion has changed somewhat.

Proposed functionality

Remove the VLAN group field and replace it with the Open Selector. This will better guide the user to make fewer incorrect selections.

The topic Multiselector for the Tagged VLAN field is suggested here as FR.
https://github.com/netbox-community/netbox/issues/15530

image

If possible, it would be good if the following fields are also preselected:

  • Tenant group
  • Tenant
  • VLAN group
    image

Use case

We group the VLANs by location. We almost always have the same VLANs at all locations. If you do not select the VLAN group filter on the device interface, you may end up using the wrong VLAN.

Database changes

No response

External dependencies

No response

Originally created by @LHBL2003 on GitHub (Feb 26, 2024). ### NetBox version v3.7.1 ### Feature type Change to existing functionality The original idea behind this feature request was to save the VLAN group filter field. Due to a revised proposal on the subject of tagged VLANs (https://github.com/netbox-community/netbox/issues/15530), my opinion has changed somewhat. ### Proposed functionality Remove the VLAN group field and replace it with the Open Selector. This will better guide the user to make fewer incorrect selections. The topic Multiselector for the Tagged VLAN field is suggested here as FR. https://github.com/netbox-community/netbox/issues/15530 ![image](https://github.com/netbox-community/netbox/assets/46369917/9308ec71-bcb9-4f42-b3e9-c403401cfcfa) If possible, it would be good if the following fields are also preselected: - Tenant group - Tenant - VLAN group ![image](https://github.com/netbox-community/netbox/assets/46369917/320427d9-b6aa-42bc-a6a9-a4eba80ac013) ### Use case We group the VLANs by location. We almost always have the same VLANs at all locations. If you do not select the VLAN group filter on the device interface, you may end up using the wrong VLAN. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closurecomplexity: medium labels 2025-12-29 20:47:56 +01:00
adam closed this issue 2025-12-29 20:47:56 +01:00
adam commented 2025-12-29 20:47:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 4, 2024):

It wouldn't make sense to enable this behavior for a single field, and enabling it more generally would require a lot more consideration around the specific implementation: UI controls, example workflows, potential trade-offs, etc. @LHBL2003 would you like to add more detail to your proposal?

@jeremystretch commented on GitHub (Apr 4, 2024): It wouldn't make sense to enable this behavior for a single field, and enabling it more generally would require a lot more consideration around the specific implementation: UI controls, example workflows, potential trade-offs, etc. @LHBL2003 would you like to add more detail to your proposal?
adam commented 2025-12-29 20:47:57 +01:00
Author
Owner
Copy Link

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

I don't know what other details to add?
I also don't know where there are other fields that serve as filters and are not cached. Currently I only know "VLAN group" which serves as a filter in the properties.

The only main wish I have here is to save the selected value of VLAN group.

I know this is a filter field. But why doesn't it make sense to save it? After all, in my opinion, 99% of the time you select it over and over again.

Maybe you can tell me why it makes no sense to save the VLAN group field?

If you only have 5 VLANs, this may not matter. But if you have the same VLAN about 120 times at each location, then it's a different story. Or am I seeing this wrong?

@LHBL2003 commented on GitHub (Apr 5, 2024): I don't know what other details to add? I also don't know where there are other fields that serve as filters and are not cached. Currently I only know "VLAN group" which serves as a filter in the properties. The only main wish I have here is to save the selected value of VLAN group. I know this is a filter field. But why doesn't it make sense to save it? After all, in my opinion, 99% of the time you select it over and over again. Maybe you can tell me why it makes no sense to save the VLAN group field? If you only have 5 VLANs, this may not matter. But if you have the same VLAN about 120 times at each location, then it's a different story. Or am I seeing this wrong?
adam commented 2025-12-29 20:47:57 +01:00
Author
Owner
Copy Link

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

Hello Jeremystretch,

So I have reworked the case https://github.com/netbox-community/netbox/issues/15530 with another idea. I have also revised this suggestion again. I hope you like this idea. See above.

Personally, I have a good gut feeling that you might like this idea :D

@LHBL2003 commented on GitHub (Apr 5, 2024): Hello Jeremystretch, So I have reworked the case https://github.com/netbox-community/netbox/issues/15530 with another idea. I have also revised this suggestion again. I hope you like this idea. See above. Personally, I have a good gut feeling that you might like this idea :D
adam commented 2025-12-29 20:47:58 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 22, 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 22, 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:48:00 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 21, 2024):

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 (Sep 21, 2024): 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.
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: medium 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#9294
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?