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"

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?!

Please consider this update - bugbear for our business is the basic search functionality on the portals and they need something more extensive

The "Request contains..." in the Search field is misleading.  At least for now indicate there how that field really works.

Hello,

This does not seems like a complicated functionality, can you add it to the roadmap please?

Search in names is also bad. You can't search part of the word. You need to search for whole word.

I agree with @Chris Naurois we would like to have that ability too.

There is one very critical thing - issues search controls searches only on names of issues. It does not search on content of issue and on communication content. Customers would like to search for all the issues where specific word or phrase are mentioned

There is a high demand from users to be able to utilize better functionality with more filters when searching issues reported from within the customer portal.

I would second this (voted).
We have clients with hundreds of tickets, and they need to search across more fields (including customs, that would be ace), and having a LIKE("%abc%") incorporated rather than an exact match.
At the moment, when they cannot find their ticket, they recreate a new one and our SLAs are exploding.

Searching in customer portal needs improvement.

A customer should be able to search for creation date, for example.

It would be great if you could perform searches as you can in JIRA.

The way that the search function uses only the summary field is disappointing. Showing results where the search term appear in the description, issue type, reporter and assignee, etc. would be a huge jump in functionality.

Customers should be able to search for any keyword that is used in a ticket.

After more reflexion, i think it's will a good idea to use same filter mechanism as jira project.
As admin i configure filter for my customer and i publish it to JSD portal. For example i can create a filter for each workflow status or by priority or by customer field and so on.

We need this function, our company work with operator so we have a lot off issues by customer. Sometimes the customer create same issue. With the search function, the customer can verify if the issue is "new".