Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ASN Range search does not work #18213

Closed
dmulyalin opened this issue Dec 12, 2024 · 0 comments · Fixed by #18219
Closed

ASN Range search does not work #18213

dmulyalin opened this issue Dec 12, 2024 · 0 comments · Fixed by #18219
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@dmulyalin
Copy link

Deployment Type

Self-hosted

Triage priority

N/A

NetBox Version

v4.1.7

Python Version

3.10

Steps to Reproduce

  1. Go to IPAM -> ASN Ranges
  2. Add new range, give it a name, do not add description, save
  3. Try to search range by name either using using quick search field or by using IPAM -> ASN Ranges -> Search TAB

Searching using global search works, since this was fixed as part of this issue #17537

Expected Behavior

Searching ASN range by name works for both:

  • IPAM -> ASN Ranges -> Search TAB
  • IPAM -> ASN Ranges -> quick search field

Observed Behavior

Searching ASN range by name does not works for:

  • IPAM -> ASN Ranges -> Search TAB
  • IPAM -> ASN Ranges -> quick search field
@dmulyalin dmulyalin added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Dec 12, 2024
@jeremystretch jeremystretch self-assigned this Dec 12, 2024
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants