cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Is it expected that new search is useless and need to wait proper implementation?

Viachaslau
Guide

Just simple comparison on how new search is bad:

Viachaslau_0-1684147200710.png

 

4 REPLIES 4

GabrieleHB
Dynatrace Enthusiast
Dynatrace Enthusiast

Hi @Viachaslau. Selecting the second result ("Search support resources") will get you the results you're looking for.

step1.png

step2.png

The results would now include all relevant support resources, not only results from Documentation. If this isn't sufficient to address your use case, I encourage you to suggest a Product Idea, and if this is sufficiently supported we can consider reintroducing doc results in the search.

Viachaslau
Guide

Ok, well It was concept "navigation in the app via search" 
Was - context real time elasticsearch, with real time links to settings, menu, external links
Just get all you need- do 1 click

Now
- blind search, navigate, click, click again
Brilliant UX) 

 

Try to jump to any internal setting now:

Viachaslau_0-1684160173019.png

 

GabrieleHB
Dynatrace Enthusiast
Dynatrace Enthusiast

Searching for settings will be available early next quarter, and will be followed by searching for Hub listings. We're also working on improvements for searching for monitored entities.

Viachaslau
Guide

Ok, please don't do worse than it was
E.g,. Just in the 1-st example in old search you can see context and 3-5 matched results for "alerts" search token

Now.... just click inside "search resources" and maybe here will some answer
It is set back to maybe 20Y old UX before very first inline search was invented...
(technically the is inline search but UX doesn't use its benefits.)
Peoples in commerce are fighting for every click in conversion goals...