-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 2023-06-21] Use the same component for the different states in ValidateCodeModal #16424
Comments
Job added to Upwork: https://www.upwork.com/jobs/~012154682b55de640e |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @sobitneupane ( |
Making this a weekly, I'll do my best to get it done at the end of the week as this could also be implemented on the plane |
on my radar for the next days |
on hold for now. It's better to first migrate the |
Oh yes this could be off hold now. |
Making this |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.27-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 2023-06-21. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
Hmm.. it looks like no BugZero team member was assigned. Asked for help on Slack |
@cristipaval, @sobitneupane Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
bumped BugZero team in Slack to handle the payment |
Paid Sobit on New Dot |
Closing as Sobit was paid. |
Coming from this.
Refactor the code in
ValidateCodeModal
package and reuse the same component for multiple states to avoid code duplication.Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: