Fix v.8 search results?!?

SOLVED. I just re-downloaded and started using 1P7, which is the default download for the Mac App Store. This fixed my search issues, and fixed the key-command (cmd - /) for auto-populating input fields in browser. It also fixed the sporadic functioning of my fingerprint reader on my MBP. Everything just works perfectly, again.

I highly recommend downgrading until 1P8 is ready for consumers.

@Jack.P_1P and 1P_PeterG - with all due respect, would you be able to forward my workflow to the rest of the dev team?

I would love their eyes on my use case since it is so explicit. I know your team implemented the new search bar to improve functionality, so perhaps I need to learn new ways! But feedback is valuable at any stage in development, and I have outlined clearly how this is a step backward (for me, and several users here).

Additional note: I have been a huge advocate and paying customer since 1Password 3. I work in development and have recommended / set up over two dozen clients with 1Password. Writing in a forum or complaining about a feature is not my m.o., but it shows how important this product is and continues to be. So, kudos to the team for your excellent work over the years.

@malte83 it's even worse. The problems with the so called "nextgen serach" were reported almost a year ago during early access. It took ten months to get at least sub string search back. I fear it will take another 10 months for them to fix/revert the hardly usable search UI.
I'm using 1PW more or less since its first version was release and following this forum for many years. I've never seen complaints about the previous search but a lot about 1PW8's one. The reason for the change was never mentioned even after repeated requests.

I upgraded to v8 a little while ago and I totally agree with the other users, the search function is a huge step backwards and it should behave exactly like in v7 to be user friendly. @milesr example is on point.

I almost cannot believe, that now three months after the initial post, little progress has been made.
Also sadly no answer to @peet1 question why this change has been made in the first place.
At least you could have added an switch in the settings to enable the old search behavior.

*I would assume many users are frustrated with the new design and don't voice their opinion.
*
Just to put some weight on how bad it actually is: If I'm still required to use CMD-OPT-F to have an search experience close to what v7 was in four weeks from now, I will dedicate one hour of my life to look for an alternative to 1PWD and cancel my subscription.
I just put an reminder on my todo to follow up on this.

I have bought my first 1Password4 License in 2014 and have been an paying customer since

Still cannot believe how this bad search-UX design is still not rectified.
It is the biggest leap backward since I use 1Password.

Thanks to everyone for starting this topic. I want to point out a use case in finding "AWS" credentials using V8 versus V7 to illustrate how this doesn't work...

1Password Version 8 - Current Search
1. Click on the Search Bar
2. Type "AWS" to find your AWS credentials.
3. Click on your result ("AWS Console").
4. Read result and determine it's for the incorrect AWS service.
5. The Search text disappears altogether.
6. Type "AWS" again to find your AWS credentials.
7. Dangit... you clicked the same credential or the wrong credentials.
8. Type "AWS" again to find your AWS credentials!
9. You found the correct credential to use.

1Password Version 8 - Filter
1. Use cmd-option-F to bring up Find Bar. (Another key-command to remember)!
2. Type in "AWS."
3. Click through live listings.
4. Find the correct credential to use.

1Password Version 7 - Filter
1. Click on Search Bar. (Easiest)!
2. Type in "AWS".
3. Click through live listings.
4. Find the correct credential to use.

1Password Version 7 had it right and I hope the team brings the option back to use this previously amazing capability to the Search UI space without additional key-commands.

But, if we are doing the search as the replacement - why does the user input text disappear after submitting? User input doesn't disappear after doing a Google Search or Apple Spotlight Search. So why does this make sense here?

Apologies for the directness of this post, 1Password is an integral part of my workflow and business and is wholly beloved. But the V8 workflow just doesn't feel as seamless as prior versions.

Hi folks,

Thanks for your feedback on this. Version 8.9.4 of 1Password for Mac brings improvements to substring searching. Let me know how you get on with that, or if there's still places where search doesn't behave as you'd expect.

Jack

+1
Adding my voice to the wish for a return to the v7 search behavior.
Truth is, I don't need "search" half so much as "filter" which is what the v7 search provided.

The "search and jump to" functionality here is simply infuriating. I'm left to scroll through all of my logins in search of the one I actually want... ugh... may as well not have a search. You may be saying... "Well, you can use the prompt to select one of the possible matches." But I can't. It doesn't show all of the partial matches.

That said, it's nice to have the "Find" "feature", but it's a filter. Which is great, but why not call it filter? And why not give me the option to make this my preferred default behavior in the search box?

Final thought on the semantics of this: In many other solutions, Find typically feels more specific in nature ("I want to find exactly this thing"), while Search feels broader ("I am searching for something like this"), in v8 you seem to have this reversed.

+1. the "Find" feature is completely undiscoverable. just make search work like 7. this is a major workflow killer.
I've used 1pass for a while and loved it. i know yall have worked hard on this v8 upgrade, but it sure is making it hard to love.

Whoever "invented" the so called next gen search has never ever used it or any previous version of search. I've reported the problem in September 2021 and the only change was the addition of find.
The new UI with its extra step is just not annoying. Even worse, the search is no longer able to search for substrings, it arbitrarily breaks search phrases into words and concatenates them with boolean or.

I don't believe they are willing to change anything after being told for months that it's an ongoing area of work without any visible progress.

Oh hey, I hadn't even noticed the "find" feature. After a little experimentation here, I'd say it's not the most keyboard-friendly implementation, but it's definitely helpful. Between "find" and "search" with its two modes (return versus cmd-return), it seems all the search functionality I want is in there, but man, is it confusing, and it seems like the default behaviors are antithetical to my most common usage patterns.

You guys have a good starting point functionally speaking, but I think you need to go back to the drawing board in terms of UI/UX. It's kinda a mess for both beginners (e.g., the terminology itself - "find" and "search" are synonyms for most people in most contexts) and power users (filter discoverability and limitations).