starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-14 14:23:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

allow filtering of interfaces in the gui by 802.1Q Mode #10931

New Issue
Closed
opened 2025-12-29 21:37:54 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:37:54 +01:00
Owner
Copy Link

Originally created by @ITJamie on GitHub (Mar 21, 2025).

Originally assigned to: @pheus on GitHub.

NetBox version

v4.2.5

Feature type

Change to existing functionality

Proposed functionality

add 802.1q mode as an option on the interfaces filter form.

Use case

currently in the interfaces filter gui theres no option to filter by 802.1q mode. its possible to filter it right now by adding ?mode=tagged-all to the interfaces ui.
filtering by poe mode is already an option so its a bit odd that 802.1q mode isnt available

Database changes

n/a

External dependencies

n/a

Originally created by @ITJamie on GitHub (Mar 21, 2025). Originally assigned to: @pheus on GitHub. ### NetBox version v4.2.5 ### Feature type Change to existing functionality ### Proposed functionality add `802.1q mode` as an option on the interfaces filter form. ### Use case currently in the interfaces filter gui theres no option to filter by 802.1q mode. its possible to filter it right now by adding `?mode=tagged-all` to the interfaces ui. filtering by poe mode is already an option so its a bit odd that 802.1q mode isnt available ### Database changes n/a ### External dependencies n/a
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:37:54 +01:00
adam closed this issue 2025-12-29 21:37:54 +01:00
adam commented 2025-12-29 21:37:55 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (Apr 13, 2025):

Hi @jnovinger,
I'd like to contribute this. Would you mind assigning the issue to me?

I’ve already implemented the feature and chose to use a MultipleChoiceFilter for the mode field, which would be a breaking change. Would that be acceptable, or would you prefer I stick with a single mode filter? This could potentially be included in the upcoming v4.3 release.

I went with a MultipleChoiceFilter as it feels more consistent with how PoE mode filtering is handled, but I’m happy to adjust based on what works best for the project.

@pheus commented on GitHub (Apr 13, 2025): Hi @jnovinger, I'd like to contribute this. Would you mind assigning the issue to me? I’ve already implemented the feature and chose to use a `MultipleChoiceFilter` for the `mode` field, which would be a breaking change. Would that be acceptable, or would you prefer I stick with a single `mode` filter? This could potentially be included in the upcoming v4.3 release. I went with a `MultipleChoiceFilter` as it feels more consistent with how PoE mode filtering is handled, but I’m happy to adjust based on what works best for the project.
adam commented 2025-12-29 21:37:55 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 14, 2025):

@pheus assigned to you, thanks!

@jeremystretch commented on GitHub (Apr 14, 2025): @pheus assigned to you, thanks!
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 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#10931
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?