1Password 8 for Mac cannot filter search by Vault

this thing that you cannot easily search and filter the results by vault is a disaster. Very disappointed. Lost confidence in 1Password. I should have waited to upgrade to 8. But you folks have been doing a great jobs for years. So I upgraded without waiting. Great Mistake! You should never release an unfinished upgrade. This is far more important than any new things you added to 8

Have a great weekend all. I've recorded the feedback for the team.

ref: IDEA-I-1480

OK, I've adjusted to the collections. I'm good with it....just have to give up thinking like version 7 and adjust to the 8 way of doing things. Just going to treat it like a new app and forget the old workflow....from that clean slate perspective I'm liking it....

I recently upgraded and read the forums and reviews beforehand and got an idea of what the complaints were before taking the dive. Once I did, I made it a point to read as much of the documentation on the new version to seek out what changed in the features I used most so I could anticipate the friction presented to my muscle memory. While I can't say I hate everything, I can't say it's been frictionless either. So far my biggest muscle memory annoyance is the per vault search functionality. I did quickly find the cmd-f keystroke and am glad it's at least there, but it just doesn't feel as fast to use as I was used to in the prior version despite it really only being one extra step before typing the search term. I just wish that the search scope in the search bar would just automatically change to the specific vault that is actively selected. If that's not everyone's cup of tea then I'd like at least for it to be a setting that can be configured.

I would still like to see them add the filter text box. With the amount of Vaults my company has shared, instead of needing to know the full exact name of the vault for the =vault: command to work or scrolling through the entire list it would be much more appreciated to just bring that filter vault field back. We have users Re installing version 7 of the client in droves because of how much they dislike the version 8 feature removal.

I want to add +100 to what camner said here:

I think a lot of the issues people have raised in this thread would have been at least partially addressed by 1P being more explicit about the changed functionalities in v8 and the rationale behind those changes

I don't feel like a valued paying customer when I'm struggling to figure out what your closed source app does. Open source has problems, but at the least I can see the PRs that got merged or read the source and figure out what's intended. I'm happy to pay you, but please stop making me feel blind to where you are going.

Most points have already been made, I just want to communicate that I was a heavy user of the "remove vault from all vaults" functionality. I would have specific vaults for places I've lived and remove them from the search when I move away (kind of like using it as an archive). The new collections functionality does provide all that I need, but it was very hard to figure it out.

I see how collections are powerful and I am excited to use them. I do think that this is a good direction for 1P overall, but I do feel deceived by that feature seemingly "disappearing". It would've been much nicer if I had an automatic new collection created with my previously "enabled" vaults from all vaults and a dialog saying "use this collection to continue the same way as before".

camner hits the nail on the head, and not just for the specific features in this topic, but all the features that have either been removed or replaced by alternative means. From-scratch rewrites allow lots of freedom and a way to eliminate technical debt, likely for good reasons, and hopefully with an improved product in the end. Thus far, IMO, 1P8 has overly simplified the experience, at the expense of known-good workflows/features from 1P7 and before.

Request: Publicly address this and other concerns in a constructive way, and don't hide behind "I've notified the devs" or "we keep our roadmap secret" statements - as a user, those are really quite frustrating and don't engender confidence.

Prediction: if 1P/AgileBits are not careful, the lack of attention to this meta-issue could cause a lot of lost users and/or ill-will.

I think a lot of the issues people have raised in this thread would have been at least partially addressed by 1P being more explicit about the changed functionalities in v8 and the rationale behind those changes. It is SO frustrating to install an "upgrade" and see that previously-depended-upon features seem to have disappeared. One doesn't know if (a) the designers took it away intentionally and have no intention of restoring it, (b) it didn't make the cut before the upgrade was released but is in the roadmap for the future, or (c) it IS present, but the UI has changed and the user hasn't figured out yet how to access the feature in the new version.

Evernote did a pretty darn decent job of doing this. When they rewrote from the ground up, at first (non beta) release there was (lots of!) previous functionality missing, but they were very open about whether the missing functionality was part of the roadmap or not. AND (and this is crucial, IMHO), Evernote was VERY good about listening to their user base and changing their decisions about features as they heard from the user base. They definitely brought back some of the functionality that their original rewrite did not intend to include, and sometimes the way the feature was restored was even better than in the previous version.

I think I understand why 1P wants us to get away from using vaults as our primary organizing method. I always felt that it was a bit of a kludge, because vaults were originally really intended (I think...) to be a method of giving differential access to subsets of one's 1P data (which is why vaults originally had their own individual password, if I remember correctly). But since 1P didn't have other ways of designating subsets of data (without regard to access rights), people started using vaults for that purpose (including me). This thread shows the extent to which some people have deeply depended on this, and understandably are frustrated when, "poof," it's gone. It totally screws up their workflow.

1P could have done a MUCH better job of anticipating the s&*tstorm this would cause and proactively addressed these issues as part of the actual release.

Jack_P_1P

Thanks for returning a v7 feature: in the browser tool the ability to restrict a search with the 1P icon! However, it appears to restrict by vault (awesome) but not by collection (oddly inconsistent with the direction 1P seems to be going). Other notes:

1) a ⌘ key combo should be a shortcut to a gui mouse-able action, not the only way to accomplish a common feature.

2) "Additionally, you can customize which collection is used by Quick Access by clicking the icon in the search bar."
Great. But this is by collection only and not vault, the opposite of the browser extension.

3) "Quick Access, Search in the main app, and 1Password in the browser all use slightly different search methods, due to the different contexts that they're in." I understand that suggestions are contextual. But this makes no sense for search results and is simply infuriating and tedious for the user. If I'm searching, I'm telling you what I want, you aren't inferring it from context. For example, if I search "apple," I have literally dozens of results in all vaults, and even several when I limit the search to a single vault. If each tool gives me different results, and I can't narrow further by limiting the search to the title field, then I'm spending all my time visually scanning long lists that are different all the time, i.e., the search is ineffective. Even if the results order changes over time (a frequency of use-based order), that's fine as long as it is consistent between the three tools.

I like collections. It's a great abstraction. But it does not in any way eliminate the need to limit searches and views by vault. If it did, why even have vaults? It also feels like the three tools are developed by different teams that don't talk to each other or share libraries.