Earlyflash

Question for you all; how are you going about managing the PRs from the community that seem to be 'stuck'?

Looking at the client github repo, there are 55 PRs, mostly from the community, the oldest of which is 2.5 years old.

This doesn't seem like a good way to interact with your community. After 2.5 years, you know if it is or isn't going to be merged, so you should say so. The silence is poor community behaviour and will ultimately lead to forks and a lack of interest.

I posted this elsewhere on the thread, but figured it would make sense to put it top level too.

I have a stupidly long email address, and when adding a new login, it is hugely annoying to have to type that in every single time into Bitwarden.

I can’t tell you how frustrating this is! can you not just have a list of predefined account names to pick from? I think there was an iOS PR for this on the repository, but it still doesn’t work.

This is 100% the biggest challenge to get my family to switch over; they hate the workflow on adding a new account.

Agree that PRs don't always move forward, but the worst possible outcome is 'limbo'.

After 2.5 years you *know* if you are going to merge it or not, you should put the submitter out of their misery.

A good example:

https://github.com/bitwarden/clients/pull/2047

Nearly a year ago, it was approved in principle!

I'm not trying to get on your back over this; but if you run githubs and PRs then it's a key responsibility to at least respond to requests from the community. In a business context we'd set an SLA to at least respond.

This is my #1 gripe with BitWarden. I believe there’s even a community PR for it; but we still do t have the functionality.

It’s got me close to leaving the BW ecosystem multiple times. I have a sadly very long email address and typin lg it in its seriously frustrating

Not to be funny, but this has been a feature request for over two years! It doesn’t inspire confidence that it’s still not done!