-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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-08-02] [$250] Migrate ReportSettingsPage.js to function component #16250
Comments
I'd love to work on this. |
Whoops! This issue is 2 days overdue. Let's get this updated quick! |
6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it! |
12 days overdue now... This issue's end is nigh! |
This issue has not been updated in over 14 days. eroding to Weekly issue. |
I'm interested to work on this |
Can I work on this? |
I can work on this issue. |
Can I work on this? |
Job added to Upwork: https://www.upwork.com/jobs/~01248a2f79831e8cf8 |
📣 @fedirjh 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @alexxxwork 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Upwork job |
@NicMendonca @fedirjh I am going to be going OOO till Monday July 24th. If you need engineering import before then, feel free to remove me and re-apply the label to reassign it. |
If it is available I am open to work on it |
The PR is ready |
@deetergp, @alexxxwork, @NicMendonca, @fedirjh Eep! 4 days overdue now. Issues have feelings too... |
@MelvinBot the PR is merged |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.45-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-08-02. 🎊 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.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
|
@NicMendonca Payment is $250 for both Contributor & C+ |
@fedirjh why? 😅 Where did we agree that? |
okay - updated this to $250: #16250 (comment) |
@alexxxwork @fedirjh you both have been paid via Upwork |
@NicMendonca I was assigned to this issue on jul 15 and the PR was ready the same day. It was reviewed and approved by C+ on jul 18 (that is 2 business days since assignment) and we were waiting for @deetergp to approve changes but they were OOO for that week (from 17 to 23 jul). While this PR hadn't been merged there were two other PRs changing this component so I've updated the code twice to include changes. Could this issue be eligible for speed bonus taking in account the details above? |
@alexxxwork thanks for following up! We've agreed internally that it's 250$ flat payment for all functional components migration and they are not eligbile for speed bonus. |
@NicMendonca Thanks for clarification! |
Class Component Migration
Filenames
React.Component
Task
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: