Search Function seems broken

Howdy sourpeachy ,

In my experience, using wildcards on both sides is the best way to return all results you're looking for that contain a specific value. I'm not sure that what you're experiencing is a bug, just how it is designed to return results.

There may be some other useful tips and tricks in our Advanced search and syntax rules.

When I attempted to replicate your scenario, I didn't see the same issues. If you manually re-type to replicate that scenario, does it still happen? Is it possible that the title of that ticket may include special characters we can't see?

Hi SPSDude This is an odd one, because if you put it into another titled the same, it works! But on the "broken" one, if you modify the title and put it before the sequence of numbers then it works. As soon as you put it after, it does not work again. Not sure what is going on, I believe there to be a bug, but our developers are claiming that we just "aren't using the system correctly" but I am trying to prove that something is broken because this happens alot. Any text after the sequence of 6 numbers is not searchable on the broken incidents.

Now, after modifying that title after several attempts to test, it now shows in searches but having the same title when it was broken.

sourpeachy , let's look into this further. Can you email me so we can engage with support? It's always nice to confirm WHY a search isn't yielding the expected results.

sean.sebring@solarwinds.com

sourpeachy , let's look into this further. Can you email me so we can engage with support? It's always nice to confirm WHY a search isn't yielding the expected results.

sean.sebring@solarwinds.com