-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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-17] [Payment card / Subscription] Integrate failed billing scenarios banner with backend data #42431
Comments
Hi, I'm Eugene from Callstack - expert agency - and I would like to work on this issue. |
Not overdue |
Today's updates - WIP, implementing utils file to handle all predefined error cases |
Today's updates - WIP, implementing utils file to handle all predefined error cases |
Today's updates - WIP, still implementing utils file to handle all predefined error cases |
Just cross-posting from here so that the message does not get lost: let's ensure to include the RBR implementation for when switching between plans is disallowed (failed |
Today's updates - WIP, Utils file is mostly done, remained - to glue logic with buttons, add error cases from failed API commands |
For the next two weeks I will be OOO, on Monday will be decided who will continue to work on this task |
Reassigning to @blimpich since I'm headed out on extended leave after today |
Hi, I'm Julian from Callstack - expert agency - and I would like to work on this issue. |
@blimpich, @JKobrynski Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Adding @mananjadhav as they'll be the C+ reviewing the PR |
The title is also a bit misleading, it's not only integrating with backend (making actual API call). Scope also includes adding this |
@mananjadhav, @blimpich, @JKobrynski Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Reviewed the PR again sometime back. |
PR merged yesterday, adding labels to get a BZ assigned. |
Triggered auto assignment to @miljakljajic ( |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.5-13 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-17. 🎊 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 pay you in ND right @mananjadhav ? So just a payment summary be due for this one on the 17th? |
Yes @miljakljajic that's right. |
Thank you! |
I'm going to submit the payment summary today as I'm OOO tomorrow - please don't request payment until tomorrow: @mananjadhav is owed 250 USD for their work reviewing this issue |
Design doc
Issue Owner
Current Issue Owner: @miljakljajicThe text was updated successfully, but these errors were encountered: