-
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-02-07] Fix console errors with Locale Picker #14637
Comments
@maddylewis, please mark @Prince-Mendiratta as the reporting contributor here and make a reporting bonus Upwork job. Thank you! 🙇 |
can do! i'll leave a comment here once the contributor has been paid 👍 |
@Prince-Mendiratta, we're going to move forward with paying you the reporting bonus because you provided an RCA and a solution. Please note that this won't always happen. Our guidelines have more details, but essentially, we want to pay you for the urgency and quality of your post here: Just know that in the future, this type of comment wouldn't actually qualify for payment. |
Job added to Upwork: https://www.upwork.com/jobs/~0105b02a675ed86a5e |
Current assignee @Santhosh-Sellavel is eligible for the Internal assigner, not assigning anyone new. |
Thank you @Luke9389! What should've I done instead after figuring out the RCA and solution? |
You would post those as a proposal on this issue. So I would say, don't start with an RCA until there's an External issue for the bug. |
@Prince-Mendiratta - can you apply to this job so that i can process your payment? thanks! |
@maddylewis It's probably an internal job, it says "access denied" to me and that I have to be invited to view the job Can you please send me an invite? This is my profile at upwork. |
Not sure why I was not assigned as C+ to handle the RCA as per the process. This is a progressive change to the original PR #12447 (comment). That said, this issue does not qualify for C+ payment. |
My apologies @parasharrajat, this is my fault. @Santhosh-Sellavel was automatically added to the PR by melvin-bot, so I just assigned him here because he already had the context for the problem.
Would you explain why this is the case, please? |
IMO, and as per process because this comes under RCA and the original PR is still under regression period. Technically, I should have reviewed it as part of the original PR. But I leave that part to BugZero assignee and you. |
Ah OK. In the future, I'll follow that process. Since I made the mistake, I think we should pay @Santhosh-Sellavel for his review work on the PR. He tested on all platforms and verified the code. Sorry about that. This will not happen again. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.62-1 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-02-07. 🎊 After the hold period, please check if any of the following need payment for this issue, and if so check them off after paying:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@Prince-Mendiratta - i've invited you to the job 👍 |
@maddylewis Accepted, thank you! |
@Prince-Mendiratta has been paid. @Luke9389 - just making sure we're all set here before i close this one out. this issue was only created to get the reporting bonus processed, ya? lmk! |
Yep, we're good to close this out. Thanks! |
bump @Luke9389 @maddylewis |
@Santhosh-Sellavel - will you confirm the amount you're expecting for payment? |
I'm not sure, we usually pay $1000 for internal PR reviews. If you feel the bounty should be reduced let me know the amount, thanks! cc: @Luke9389 @maddylewis |
okay gotcha. @Santhosh-Sellavel - will you link the issue that this comment is on? i just want to make sure im processing this one correctly. ty! |
On this issue is only here -> #14637 (comment) |
I'm in agreement here. Sorry, I closed this out prematurely. |
ok great! i'll get that payment processed shortly. |
@Santhosh-Sellavel - will you share the name on your Upwork profile so that I can invite you to the job/process payment? |
okay @Santhosh-Sellavel has been paid! sorry for the confusion! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Context
This issue covers the fix for a bug pointed out here: #14526 (comment)
The RCA is accurate and the fix is effective.
The original PR that caused this is here: #12447 (comment)
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: