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

Decrease live search minimum characters #2613

Closed
candlerb opened this issue Nov 27, 2018 · 3 comments
Closed

Decrease live search minimum characters #2613

candlerb opened this issue Nov 27, 2018 · 3 comments
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@candlerb
Copy link
Contributor

Environment

  • Python version: 3.5.2
  • NetBox version: 2.5-beta2

Steps to Reproduce

  • Create device type "patch-24-rj45"
    • Add one rear port called "backplane", 8P8C
    • Add 24 front ports [1-24], linked to backplane:1 to backplane:24
  • Create device role "patch panel"
  • Create "PP1" in rack position U48, with this role and device type
  • Create "PP2" in rack position U47, with this role and device type
  • While PP2 is open, click the 'connect' icon next to its "backplane" rear port
  • Try to search for the corresponding "backplane" port on PP1

Expected Behavior

After entering "PP1" in the Device, and selecting "Rear Port" from the type, the port "backplane" would appear in the Name field.

Observed Behavior

The "backplane" port did not appear.

image

Workaround

Use the alternative way of selecting the partner device, by following the hierarchy of site-rack-device.

image

@candlerb
Copy link
Contributor Author

Update: if I change the names of the devices to "PAN1" and "PAN2", and after typing PAN1 I wait for it to pop up in the drop down and select it from there, it works.

Hence it seems to be because the name search doesn't kick in until 4 characters have been typed.

@jeremystretch jeremystretch changed the title Partner port not appearing in Connect dialog Decrease live search minimum characters to 3 Nov 27, 2018
@jeremystretch
Copy link
Member

Correct. The livesearch widget currently requires a minimum of four characters before it will initiate an API request to populate selection list. I'm okay with reducing this to three, but any fewer is probably going to be more of an annoyance.

@jeremystretch jeremystretch changed the title Decrease live search minimum characters to 3 Decrease live search minimum characters Nov 27, 2018
@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application status: accepted This issue has been accepted for implementation labels Nov 27, 2018
@jeremystretch
Copy link
Member

FYI this was pushed to develop since it's not pertinent specifically to the beta.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants