-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 2024-03-04] [$250] [MEDIUM] Bank account - "PO boxes and mail drop addresses are not allowed" appears twice in Address #36500
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
Triggered auto assignment to @arosiclair ( |
We think that this bug might be related to #wave5 |
Job added to Upwork: https://www.upwork.com/jobs/~017b8183bbc1eecc39 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat ( |
@shubham1206agra @akinwale @MrMuzyk @Swor71 minor design issue |
Upwork job price has been updated to $250 |
📣 @akinwale 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
ProposalPlease re-state the problem that we are trying to solve in this issue.Bank account - "PO boxes and mail drop addresses are not allowed" appears twice in Address What is the root cause of that problem?We render the What changes do you think we should make in order to solve the problem?We should remove the warning from top of page here:
|
ProposalPlease re-state the problem that we are trying to solve in this issue."PO boxes and mail drop addresses are not allowed" appears twice in Address What is the root cause of that problem?We have What changes do you think we should make in order to solve the problem?We should remove
What alternative solutions did you explore? (Optional)N/A |
Based on the new BA flow design doc, the message at the top of the page is a part of the design, so we can remove the hint instead. In this case, @codinggeek2023's suggested approach in their proposal is the way to go. 🎀👀🎀 C+ reviewed. |
Triggered auto assignment to @robertjchen, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
I am good to handle this Robert, sorry for the melvin ping |
📣 @codinggeek2023 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
This also was deployed to production yesterday, did the automation fail @mountiny 🤔 |
Payment overdue @mountiny :) |
Triggered auto assignment to @joekaufmanexpensify ( |
Summary: $250 to @codinggeek2023 please |
@joekaufmanexpensify This is a regression from the VBBA refactor on which @akinwale is C+. |
Ah, got it. Thanks for confirming! |
@codinggeek2023 $250 sent and contract ended! |
@akinwale since this is a regression, I ended the contract without payment. |
Upwork job closed. |
All set. Thanks everyone! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.4.41-3
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Expected Result:
"PO boxes and mail drop addresses are not allowed" will only appear once
Actual Result:
"PO boxes and mail drop addresses are not allowed" appears twice
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: