-
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
Feature - Allow user to create international bank account #51082
Comments
Triggered auto assignment to @lschurr ( |
|
Triggered auto assignment to Design team member for new feature review - @shawnborton ( |
@shawnborton sorry for the ping. This is implementation for design doc and design is already approved by the team |
No worries, just holler if you need any help! |
Should we have External added here @MonilBhavsar or is this already assigned and being worked on? |
@lschurr, @shubham1206agra Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@MonilBhavsar Can you make this weekly? |
Making this Daily again since nothing is blocking |
@MonilBhavsar, @lschurr, @shubham1206agra Whoops! This issue is 2 days overdue. Let's get this updated quick! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.80-6 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 2025-01-13. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Payment Summary
BugZero Checklist (@lschurr)
|
Hey @MonilBhavsar @shubham1206agra I see this PR was reverted on Jan 2nd, but is now on prod. Was that a regression? What is the payment amount for this one? |
Yep, the PR was reverted and @shubham1206agra is working on a followup. So payment is not due here yet. |
Ah, great thanks! Closing this one out. |
@lschurr Please reopen this issue as the underlying issue is not yet completed |
Ah, sorry about that. Reopening. |
@MonilBhavsar, @lschurr, @shubham1206agra Eep! 4 days overdue now. Issues have feelings too... |
Any update here @shubham1206agra? Should this be made Weekly? |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Tracking issue https://github.com/Expensify/Expensify/issues/421064
Implement this section of design doc https://docs.google.com/document/d/19ltca0iKwB00pReokjBf9rEHoi1u8y-2_x-82jMibho/edit?tab=t.0#bookmark=id.183ls0sldt64
Version Number: N/A
Reproducible in staging?: N/A
Reproducible in production?: N/A
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): N/A
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL: N/A
Issue reported by: N/A
Slack conversation: N/A
Action Performed:
Break down in numbered steps
N/A
Expected Result:
Describe what you think should've happened
N/A
Actual Result:
Describe what actually happened
N/A
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
N/A
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
Issue Owner
Current Issue Owner: @lschurrThe text was updated successfully, but these errors were encountered: