-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[$250] Wallet - Prior bank account detail inputs are not shown. #54740
Comments
Triggered auto assignment to @Gonals ( |
💬 A slack conversation has been started in #expensify-open-source |
Triggered auto assignment to @Christinadobrzyn ( |
👋 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:
|
Agreed in slack this should not be a blocker |
Job added to Upwork: https://www.upwork.com/jobs/~021875146950762828799 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @allgandalf ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Draft bank account data is not being completely saved when navigating back. What is the root cause of that problem?There's missing values not being saved in the What changes do you think we should make in order to solve the problem?I think all draft data should be saved in the What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?There should be a test case that loops through all fields in the BankAccounts form to ensure they're saved as draft data. What alternative solutions did you explore? (Optional)I tried saving manually by directly using |
Hi @allgandalf, can you review this proposal when you have a moment? TY! |
Maybe the flow has changed? I can’t open the add account option this way. Screen.Recording.2025-01-07.at.15.01.32.mov |
@Gonals, @Christinadobrzyn, @allgandalf Whoops! This issue is 2 days overdue. Let's get this updated quick! |
I'm also not able to reproduce this, I'm getting the same prompt where I need to go through Plaid instead of just manually entering bank details. @Gonals do you know if this is the new workflow and this should be closed? |
I'm actually not sure, but maybe it depends on your location? |
Apparently it was reverted, I was working on |
Ah okay, then I think we can just close this since it's reverted, right? @Gonals @allgandalf does that sounds good? |
yes please |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Closing based on - #54740 (comment) |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: v9.0.80-2
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from TestRail: #52322
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 14.5/ Chrome
App Component: User Settings
Action Performed:
Expected Result:
You land back on the bank account details page with all your prior inputs shown.
Actual Result:
You land back on the bank account details page with empty fields
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6704929_1735788515638.Screen_Recording_2025-01-02_at_6.15.42_in_the_morning.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: