ProtonMail
Proton Pass Chrome Extension: process for reporting bugs is very confusing
We are happy to answer your questions about the code or discuss technical ideas.
Please complete the following checklist (by adding [x]):
- [x] I have searched open and closed issues for duplicates
- [x] This isn't a feature request
- [x] This is not a report about my app not working as expected
So if I want to report a bug in the Proton Pass Chrome Extension, I:
- Click the Proton Pass icon in my Chrome toolbar
- Click the navigation icon in the top-left of the pane
- Choose "Feedback & Help"
- Choose "Help Us Improve"
This is where it gets confusing. It loads this page filled with filenames and yarn commands. Nowhere on that page does it mention anything about bugs or feedback.
So I click on the "Issues" tab in Github and go to create a new issue. But then it tells me that bug reports should be sent to this support URL. Nowhere on that page does it mention anything about bug reports.
There is a small link at the bottom of the page called "Report a Problem" which goes to this page which then tells you to login to ProtonMail and report a problem from there. But I'm not using ProtonMail, I'm using Proton Pass.
Surely this process could be improved.
Yeah, it needs a bit of help.
Eg proton pass has trouble with Chase bank login, as mentioned here - https://www.reddit.com/r/ProtonPass/s/QNjrapkq3P. But I searched these issues but no mention of Chase. And couldn't find a reporting site on the proton website?
One giant report issues / find help page with autocomplete on everything would be pretty nice... 🙂
https://github.com/ProtonMail/WebClients/issues/398#issue-2402703690
@SimonEast, likewise. I searched for 10 minutes and solely found this. Few others would bother to even search. Per https://github.com/ProtonMail/WebClients/issues/new/choose, I expect that I'm meant to contact https://protonmail.com/support/?
As an example, I want to report a bug about how https://addons.mozilla.org/firefox/downloads/file/4344990/proton_pass-1.22.3.xpi doesn't appear to inform https://vault.bitwarden.com/#/settings/security/change-password that it's successfully saved its passkey (amongst other oddities, like not appearing with another passkey-support password manager enabled).
At least in this case, I was able to file https://github.com/bitwarden/clients/issues/11218#issue-2545518332, but most websites don't have this kind of workaround on their end.
