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

Select2 not filtering certain fields #2330

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

Originally created by @DanSheps on GitHub (Jan 31, 2019).

Environment

  • Python version: 3.6
  • NetBox version: 2.5.4
  • Browser version: Chrome 71.0.3578.98

Steps to Reproduce

  1. Go to /dcim/devices
  2. Start attempting to filter "Device Roles"

Expected Behavior

The list of available roles will be filtered based on what is input into the filter box

Observed Behavior

The list of roles stays consistent, does not filter based on what is typed

Affected Endpoints

  • Device Role
  • Device Type
  • Manufacturer
  • Tenant Group
  • Rack Position
  • VLAN Group
  • RIR (Add Aggregate)
  • VM Cluster Group
  • VM Cluster Type
  • Circuit Type
  • Secret Role
  • Rack Role
  • Front Ports
  • Rear Ports
Originally created by @DanSheps on GitHub (Jan 31, 2019). ### Environment * Python version: 3.6 * NetBox version: 2.5.4 * Browser version: Chrome 71.0.3578.98 ### Steps to Reproduce 1. Go to /dcim/devices 2. Start attempting to filter "Device Roles" ### Expected Behavior The list of available roles will be filtered based on what is input into the filter box ### Observed Behavior The list of roles stays consistent, does not filter based on what is typed ### Affected Endpoints * Device Role * Device Type * Manufacturer * Tenant Group * Rack Position * VLAN Group * RIR (Add Aggregate) * VM Cluster Group * VM Cluster Type * Circuit Type * Secret Role * Rack Role * Front Ports * Rear Ports
adam added the type: bugstatus: accepted labels 2025-12-29 17:24:54 +01:00
adam closed this issue 2025-12-29 17:24:54 +01:00
adam commented 2025-12-29 17:24:54 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jan 31, 2019):

Per @lampwins:

Looks to be a filter problem, not select2. Hitting the API directly has the same result.

@DanSheps commented on GitHub (Jan 31, 2019): Per @lampwins: > Looks to be a filter problem, not select2. Hitting the API directly has the same result.
adam commented 2025-12-29 17:24:55 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Jan 31, 2019):

Turns out several model filter classes are missing the search method (q param).

@lampwins commented on GitHub (Jan 31, 2019): Turns out several model filter classes are missing the search method (`q` param).
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 status: accepted type: bug
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#2330
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?