-
Notifications
You must be signed in to change notification settings - Fork 3k
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-04-13] [$4000] Can not focus on state field when clicking "fix the errors" while adding debit card Action Performed #14783
Comments
Triggered auto assignment to @miljakljajic ( |
Bug0 Triage Checklist (Main S/O)
|
@miljakljajic Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@miljakljajic Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
1 similar comment
@miljakljajic Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Can this be worked on externally? |
Triggered auto assignment to @johnmlee101 ( |
Yep! |
Job added to Upwork: https://www.upwork.com/jobs/~0170944b93cd7d941c |
Current assignee @miljakljajic is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat ( |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.95-0 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-04-13. 🎊 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:
|
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:
|
It's been quite a ride 😃 But now as we're close to the finish line, I have a few thoughts and questions. From the another proposal we eventually didn't use any part:
It wasn't necessary to apply much (or eventually, any) changes in
That ref lacked the
That ref's Are we proceeding with the split payment? Also, the fact that we had to basically fall back, step by step, to my original proposal (because of the discovered issues), was (from my perspective) the main reason why I missed the bonus deadline. So I would kindly ask you to reconsider the bonus assignment (even though I didn't technically have the PR merged in 3 days). Another argument for that might be that, from the beginning, I tried to help with this issue as much as I could from the external side, including GitHub and Slack discussions that, as I see it, clarified the actual scope of this issue. But this is just a kind request, I'm pushing my luck here 😄 |
@cubuspl42 Thanks for bringing this up. I was going to suggest that during payment. Anyways, please try to keep these comments to be minimal required info. I noticed that you are over-detailed many times. I agree that you were very active in this issue but the process is the same for all. So it does not qualify for a bonus. Apart from 3 days merge bonus, no additional work was done that qualifies for a bonus. In short, there is no need for a payment split as we didn't use the other proposal. Here is the new plan for compensation which invalidates the old plan.
cc: @johnmlee101 @miljakljajic |
👍 |
Contracts extended to all! Please accept so I can get you paid. Will we need a regression test for this? |
@miljakljajic "This offer is not available anymore" |
try now? No idea why it says that! |
@miljakljajic Now it was fine. Accepted 👍 |
@parasharrajat let me know if you have any trouble with yours |
@cubuspl42, @johnmlee101, @parasharrajat, @miljakljajic Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@cubuspl42, @johnmlee101, @parasharrajat, @miljakljajic Huh... This is 4 days overdue. Who can take care of this? |
Everything is settled from my side. So I guess @parasharrajat can confirm and we can close the issue. |
I couldn't find any contracts or offers for this job. @miljakljajic Can you please check it? |
Sent a new offer @parasharrajat |
Accepted @miljakljajic |
All contributors paid, contract ended, closing. |
@miljakljajic Actually, my contract is still open |
My mistake - closed! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
It should highlight the state field
Actual Result:
It does not focus (highlight) on the state field
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.2.64-2
Reproducible in staging?: Y
Reproducible in production?: y
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:
Screen.Recording.2023-02-03.at.12.26.15.AM.mov
Recording.1438.mp4
Expensify/Expensify Issue URL:
Issue reported by: @mdneyazahmad
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1675366008238219
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: