Please transition this to In Progress otherwise take this function out of your portfolio becuase it is useless at the moment....

Just piling on... We need this and would love to avoid having to pay $1K + USD annually for something that most Atlassian competitors support natively. 

PLEASE transition this to "IN PROGRESS" and fast track it to "WAITING FOR RELEASE"

In the context of the Algorithm, the Customer Portal Search uses the below two algorithms.  * The primary algorithm is the one in which the search term is matched with the Request Type name and description or Portal name etc.

• The secondary algorithm will search all issues using JQL ( Jira Query Language ) in the backend, and  for the issues found, it will get the customer Request Type which is returned in the search result. So, in this case, it's likely that the first Request Tyoe that you're seeing was fetched using the secondary algorithm for AtPro.

some of our customers have 1000s of tickets (open/closed) and they like to look through their older tickets for solutions, with current portal search functionality makes this VERY hard

Hi.

I'm not 100% sure it is fuzzy search, but suppose this plugin might be helpful until the feature is added: Better Search in Customer Portal.

not only this, this we need as well, but also seach via assignee or reporter within organization, this would help a great deal!

Enable Fuzzy Search capability both in the Customer Portal and Agents. This is very critical for all our internal customers as well as our agents to efficiently search for projects/ticket requests. Pls. put a top priority on this to be enabled. Thanks!

Any news on this? This is a REALLY important feature for us and our customers. The portal search right now is nearly useless for us.

Fuzzy Search is an important future for us.  Our Jira Service Management supports our internal customers who maintain different materials in the company.  Material numbers starts with a base number than as it moves thru the process other characters are added to material numbers.  

For example:

Base material number: 123456
After activity 1, the material number: 123456A
After activity 2, the material number: Q123456A

so on...

Our internal customers has a need to search all tickets by the base number 123456.  The result should display all tickets with material numbers that contains 123456.

Regards,

You can use this plugin My Requests Extension for Service Desk

But you need to pay for it... for pretty obvious functionality. This field is already indexed for full text search. So why not use it?!