-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2023-06-12] [Tracking Issue]Bug fixes: 2FA #19187
Comments
Triggered auto assignment to @stephanieelliott ( |
Bug0 Triage Checklist (Main S/O)
|
@stephanieelliott this feature (2FA) went out today and we instantly got bug reports from our wonderful open source community. Thankfully all are minor bugs. I have compiled a list have asked for help in #callstack. We can squash them soon 🚫 🐛 |
Awesome, thanks for the context @MonilBhavsar! |
ProposalPlease re-state the problem that we are trying to solve in this issue.Several smaller issues regarding 2FA. What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?
What alternative solutions did you explore? (Optional)-- |
Thanks for the proposal 🙇
|
For the
On it! |
I see, thanks for clarifying. That makes sense! 🙇 |
PRs are under review! |
Still working through reviews on the PR. |
Reviews completed, just awaiting merge |
PR is merged! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.23-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-06-12. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Created in Upwork: https://www.upwork.com/jobs/~016a53e935d8151e4b Extended offers to:
|
@stephanieelliott I have identified only this bug : View disrupted on small screen devices |
@stephanieelliott Unable to access the Upwork job? Do you mind sending an invite? |
@stephanieelliott you accidentally sent me job offer instead of @mananjadhav 😅 |
@stephanieelliott This one is actually reported by me. |
@aman-atg sorry, fixed that |
@stephanieelliott we didn't fix this issue here as it was out of scope and instead we'll be fixing it here in another issue |
agreed with @MonilBhavsar but since I reported the offline indicator issue first does this(#20004) make this one dupe |
Yes 👍 |
alright @MonilBhavsar @michaelhaxhiu maybe we just adjust the Issue reporter here #20004 |
@stephanieelliott I cannot access the job link. I think because of this. Can you please help? |
OKok sorry for the confusion, I think I was able to get this sorted:
Leaving the contracts open just in case I need to swap anything around again 😅, will close by EOD tomorrow once payment is issued for the remaining 2. |
Tough one @stephanieelliott. Thanks for clearing this one out. Appreciate it! |
Hey @aman-atg can you accept the offer in Upwork when you get a chance? |
hey @stephanieelliott can you also please close the my contract since we handling it elsewhere |
Triggered auto assignment to @bfitzexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Reapplying the |
@stephanieelliott Thanks, I've just accepted the offer. |
Paid out and ended the contract for @aman-atg. Sounds like we're all done here, so closing this one out. |
Here is the list of minor Tracking 2FA bugs to make a quick follow up PR and fix all of them
Two-factor
name is inconsistent https://expensify.slack.com/archives/C049HHMV9SM/p1684406403576119The text was updated successfully, but these errors were encountered: