IP8 "Default Vault for Saving"

not that this seems to matter, but here is my vote as well.

please also consider this a vote for not removing or changing functionality in new versions without clearly notifying users. this is not the first time y'all have done this, but I really do hope it's the last. this isn't a beta release. this is the release you are actively telling your users to install yet you clearly haven't finished implementing all the existing features, or you have actively decided to change the behavior your existing users are expecting. either way, you don't seem to have any documentation about this so no wonder you have multiple threads of angry users.

I don't need a beautiful new design if the functionality is going to be consistently inconsistent.

Now off to revert back to 1P7 😒

Please add my vote to the chorus. Also, it would really be great if 1PSW kept of log of the most popular feature requests voted on by the community, and their status (under consideration, accepted for a future release, rejected, etc.). I am not asking that you commit to a timeframe, but people would at least like to know that their voices are being heard. You must be collecting this data now. It would be nice if you shared this data with your loyal customers.

Another vote to add Default Vault functionality!

this is a critical feature needed

Thank you for the feedback. I've added everyone's votes to our internal tracker and forwarded your comments to the product team. 🙂

-Dave

ref: IDEA-I-2091

@1P_Dave any chance we'll ever get an update as to whether this is going to get fixed or not (and when)? seems that months of people requesting this is getting nowhere but what I imagine is a thumbs up on a backlogged ticket that won't ever see the light of day

@tumbaa

In general, we tend to play things pretty close to the chest when it comes to new features and changes since even the most solid release date or commitment can slip due to unforeseen circumstances and we want to avoid disappointing people. So unfortunately, I don't have the answer that you're hoping for but I can say that this is something that is being avidly discussed and looked into by the team.

Thanks again for the feedback. 🙂

-Dave

@1P_Dave

Please take a 2nd look at my post dated Oct 3. I certainly understand your reluctance to provide any release dates, as things can change, and you do not want to disappoint your customer base.

On the other hand, you are keeping an internal tracking list of feature requests, and you do have an obligation to your customers who take the time to make suggestions to make your product better, to give them some insight into what features you are seriously considering, and which ones, for whatever reason, you are not entertaining at this time.

Taking your internal tracking list, and publishing the top 50 most requested features and their current status (planned for a future release, under consideration, not possible at this time, etc.) is a best practice for development organizations (Proton Mail for one publishes the histogram with vote counts of all feature requests and their status on their support page). It would also be a great PR move for 1Passsword. I hope in the future you can be more transparent about your plans with your customers who are only trying to help.

Dean

I think the lack of transparency on both bug fixes and the re-addition of lost functionality is what’s pissing everyone off the most right now.

@thedean

I'm sorry for not being clear in my earlier response: we do have an existing internal tracking item to investigate the creation of a public feature request system and I added your vote and comments to that tracking item after you mentioned the idea in your previous post. Thank you again for the suggestion. 🙂

@AMonitorDarkly

I hear the feedback and hopefully this is something that we can improve in the future. I'll bring this up with the team.

-Dave