Fuzzy search

Add fuzzy search[1] to make it easier to find feature you are looking for.  In particular this helps when feature IDs have a long prefix like "projectfoo-" before the number, which is all you really want to have to type but you don't want to be overwhelmed with hits.  So, depending on how you implement the match algorithm, you might be able to type "foo32" to get your match, or if still too many hits "foo32 <word from feature title>" to further narrow.

[1] https://en.wikipedia.org/wiki/Approximate_string_matching

  • Guest
  • May 25 2016
  • Already exists
Release time frame
  • May 26, 2016

    Admin Response

    We provide advanced capabilities around Search Syntax which can allow you to optimize your results. See the details at the bottom of this support doc to see all of the different ways that you can customize your searches.


  • Attach files
  • Guest commented
    26 May, 2016 12:42pm

    The search behavior described in 'Using Aha! search' is not using approximate string matching.  It has a restricted wildcard that does not address the scenario described above.  I expect "predictive text" to know that if I type "foo 81" then it will find the feature reference projectfoo-81 (as well as projectfoo-381 and projectfoo-819 if they exist.)

  • Admin
    Ron Yang commented
    26 May, 2016 12:55am

    Sorry about that - hee above for an updated link

  • Guest commented
    26 May, 2016 12:52am

    That link is a 404.