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

Interfaces view: Search field being ignored #4978

New Issue
Closed
opened 2025-12-29 19:22:49 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:22:49 +01:00
Owner
Copy Link

Originally created by @dreng on GitHub (Jun 8, 2021).

NetBox version

v2.11.6

Python version

3.7

Steps to Reproduce

  1. Jump to view "devices -> interfaces"
  2. Enter search term on the right hand side
  3. Press enter or click magnifier glass

Expected Behavior

The table should be filtered by the entered search term.

Observed Behavior

The table is always empty, no matter what search term has been entered.

Originally created by @dreng on GitHub (Jun 8, 2021). ### NetBox version v2.11.6 ### Python version 3.7 ### Steps to Reproduce 1. Jump to view "devices -> interfaces" 2. Enter search term on the right hand side 3. Press enter or click magnifier glass ### Expected Behavior The table should be filtered by the entered search term. ### Observed Behavior The table is always empty, no matter what search term has been entered.
adam closed this issue 2025-12-29 19:22:49 +01:00
adam commented 2025-12-29 19:22:49 +01:00
Author
Owner
Copy Link

@dreng commented on GitHub (Jun 8, 2021):

This seems to be related to #6553. It is probably a more general bug, as I noticed that at least Front Ports and Rear Ports views are affected as well. I bet that every Device Components view is affected.

@dreng commented on GitHub (Jun 8, 2021): This seems to be related to #6553. It is probably a more general bug, as I noticed that at least Front Ports and Rear Ports views are affected as well. I bet that every Device Components view is affected.
adam commented 2025-12-29 19:22:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 8, 2021):

I'm not able to reproduce the reported behavior on v2.11.6. Searching and filtering the interfaces list works as expected. This was also confirmed on the public demo instance. Please elaborate on your initial post above to specify exactly what you're doing and what values you are searching for.

@jeremystretch commented on GitHub (Jun 8, 2021): I'm not able to reproduce the reported behavior on v2.11.6. Searching and filtering the interfaces list works as expected. This was also confirmed on the [public demo instance](https://demo.netbox.dev/). Please elaborate on your initial post above to specify exactly what you're doing and what values you are searching for.
adam commented 2025-12-29 19:22:50 +01:00
Author
Owner
Copy Link

@dreng commented on GitHub (Jun 9, 2021):

I think I know what the misunderstanding is here. The search field only filters the "name" values, not the "device" value. This seems logical since this behavior is similar e.g. in the device view. Maybe it irritated me that "name" wasn't the first column. It seems that I'm not the only one. :-)

I expected the "devices" column to be filtered, because I needed a list of all switches with all connections, cable peers and VLANs in order to export it as CSV. Since I haven't found any other view that covers this task I used the interfaces view, but there's no option to filter by e.g. device role or location. Since our devices follow a naming convention it would have been easy to filter the needed switches by using the search field.

@dreng commented on GitHub (Jun 9, 2021): I think I know what the misunderstanding is here. The search field only filters the "name" values, not the "device" value. This seems logical since this behavior is similar e.g. in the device view. Maybe it irritated me that "name" wasn't the first column. It seems that I'm not the only one. :-) I expected the "devices" column to be filtered, because I needed a list of all switches with all connections, cable peers and VLANs in order to export it as CSV. Since I haven't found any other view that covers this task I used the interfaces view, but there's no option to filter by e.g. device role or location. Since our devices follow a naming convention it would have been easy to filter the needed switches by using the search field.
adam commented 2025-12-29 19:22:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 16, 2021):

Ok, I'm going to close this out as it's not actually. I would suggest an export template but it sounds like you're trying export a ton of information at once: a plugin or custom script might be better suited.

@jeremystretch commented on GitHub (Jun 16, 2021): Ok, I'm going to close this out as it's not actually. I would suggest an export template but it sounds like you're trying export a ton of information at once: a plugin or custom script might be better suited.
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
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#4978
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?