-
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
[HOLD for payment 2024-06-28] [HOLD for payment 2024-06-24] [Payment card / Subscription] Integrate “Subscription size” screen with backend data and “Subscription details” section #38631
Comments
Hi, I'm Fábio from Callstack - expert agency - and I would like to work on this issue. |
@trjExpensify Yes, that will be next on my list if BE is ready. You can assign it to me already |
Perfecto! |
@MrMuzyk Huh... This is 4 days overdue. Who can take care of this? |
@MrMuzyk, Can you point me to the precise section this issue covers in the Detailed, please? I'd like to update the OP accordingly |
This one covers BE integration of Subscription Size part. There is no section that would cover the integration part in detail, we have an overall description of how it should work - https://docs.google.com/document/d/1jXV_vIsOGZuL0dMiuXDWRETAFRX64ODVAhWPtiuFXT8/edit#bookmark=id.mftmseyadzie What I will implement here is:
|
I'm waiting for this PR to get merged so I've opened a draft PR against it in order to get correct diff. Once the mentioned PR gets merged (hopefully soon as it's been approved by C+ already) I will make a proper PR with correct destination. Other than that it's good to review and working as expected. |
Triggered auto assignment to @joekaufmanexpensify ( |
PR merged |
@mananjadhav reviewed the PR as C+ so will be due payment for that. |
Sounds good! I'm about to go OOO until 2024-06-25, but don't think payment will be due before then, so not adding an additional assignee. If anything comes up before then, please post in Slack, and someone will be able to help. |
Heads up that I'm out on extended leave after today. The only thing remaining here though is payment, if there are any questions feel free to ask in #wave-collect |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.84-3 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-06-24. 🎊 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.85-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 2024-06-28. 🎊 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:
|
We have a comprehensive set of testing steps in the design doc, so I don't think we need to add an ad-hoc test here. |
All set to issue payment later this week! |
Only payment here is $250 to @mananjadhav via NewDot for C+. |
Going to close this out for now as it's otherwise all set, but @mananjadhav you're good to request payment whenever you're ready |
$250 approved for @mananjadhav |
This issue covers this section of the doc https://docs.google.com/document/d/1jXV_vIsOGZuL0dMiuXDWRETAFRX64ODVAhWPtiuFXT8/edit#bookmark=id.mftmseyadzie @fabioh8010
What we are implementing here is:
Issue Owner
Current Issue Owner: @joekaufmanexpensifyThe text was updated successfully, but these errors were encountered: