-
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-10-09] 🟡 Editing distance requests in App #22715
Comments
Huh... This is 4 days overdue. Who can take care of this? |
Held on creating requests. I'll drop this to weekly for the time being. |
Still held |
Still held |
Still held |
Off HOLD |
It seems the front-end for this needs the changes from #25707 in order to be implemented I will pull that branch and start a draft PR with it |
Having some local changes for this that I'm looking to submit for review today! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.75-12 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-10-09. 🎊 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:
|
Triggered auto assignment to @trjExpensify ( |
@trjExpensify Could you help me wrap up payment for this? I believe @fedirjh needs to be paid as a C+ for reviewing the PR. |
Job added to Upwork: https://www.upwork.com/jobs/~0136e127650fd78aa6 |
This comment was marked as resolved.
This comment was marked as resolved.
Cool, cool. @fedirjh I've sent you an offer for a flat $1k for the PR review. (Old bounty level, prior to the change at the start of Sept). |
@trjExpensify Accepted! Thank you. |
Paid, closing! |
- HELD on #22713Please follow the plan in the design doc: Edit in App.
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: