-
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 2024-07-24] [$250] [Payment card / Subscription] When clicking "Change payment", past data still shows on new form #44886
Comments
Triggered auto assignment to @mallenexpensify ( |
Triggered auto assignment to @madmax330 ( |
👋 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:
|
@mallenexpensify I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors. |
We think this issue might be related to the #collect project. |
This is minor and subscriptions in ND is still hidden for new users so we can demote |
Job added to Upwork: https://www.upwork.com/jobs/~01f36eea0f55c219c3 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Past data shows in the form when we try to change payment card or opening the add payment card page directly What is the root cause of that problem?In the App/src/pages/settings/Subscription/PaymentCard/index.tsx Lines 48 to 55 in c5eafd3
What changes do you think we should make in order to solve the problem?I don't think we need this(
|
Yeah we don't care about them putting in the same card number. Lets keep it simple 👍 |
Looks like automation didn't work for automatically assigning the contract. @Pujan92 please feel free to raise a PR. @mallenexpensify will make sure you get paid. |
@blimpich I will raise PR soon, the contract isn't assigned bcoz now I am about to get payments via Newdot. |
Noting that assign date is after eligible date, so @Pujan92 will be paid via NewDot |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.7-8 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 2024-07-24. 🎊 For reference, here are some details about the assignees on this 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:
|
BugZero Checklist:
Regression Test Proposal
|
Payment SummaryBugZero Checklist (@mallenexpensify)
|
@mallenexpensify can you confirm the checklist above so I can approve payments? |
@Pujan92, @blimpich, @mallenexpensify, @fedirjh Whoops! This issue is 2 days overdue. Let's get this updated quick! |
$250 approved for @fedirjh |
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: v9.0.4-0
Reproducible in staging?: Y
Reproducible in production?: Unable to check
Found when executing PR : #44361
Email or phone of affected tester (no customers): applausetester+en@applause.expensifail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Expected Result:
User expects that if the fields are cleared, then all fields should be cleared.
Actual Result:
The expiration date still shows from the previous card (And is in the correct format, missing a digit) and the Zip code is still showing as well.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6533470_1720126583755.Fields_are_still_displaying.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @mallenexpensifyThe text was updated successfully, but these errors were encountered: