-
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 Regression Test] Web - Chat - After refreshing the page, the input field is initially missing #11856
Comments
Triggered auto assignment to @bondydaa ( |
Should be marked as regression. I would say deploy blocker. This is serious one. |
it's reproducible on production already so that's why there's no deploy blocker |
tossing this to the pool as I'm not the most qualified to handle this |
Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@bondydaa let's re-apply the engineering label so that someone is assigned to it. Seems important to me. |
that's not exactly how our system works. the person assigned to triage (me) can chose to keep assigned if they're going to work on it or send it to our engineering pool for it to be picked up. The engineering label isn't a "you must do this" it just annoys other engineers when they have to context switch, see it's been triaged, unassign themselves again. It's marked as a daily, which I think is the correct label as well. |
Ok, I see. |
Triggered auto assignment to @isabelastisser ( |
Reviewing this now. |
I was able to reproduce it: Missing.input.field.mp4 |
Triggered auto assignment to @nkuoch ( |
New PR is reviewed by @thesahindia. |
@arosiclair thanks for quick review |
For internal engineers and C+, the BugZero (BZ) team will need some guidance on payment here, specifically the 50% penalty for - "Merged PR within 9 business days - 50% penalty". @0xmiroslav feel free to provide details as well. Nov 4th - new process with bonus for timeliness (link) |
I agree penalty would be applied from PR timeline but there's a lot of back and forth for enough reason. |
let's stick to the process. agree! |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.46-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-01-09. 🎊 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:
|
I feel like this is kinda a "perfect storm" issue with so much happening between @0xmiroslav being hired and now (process change right before, the fix doesn't appear to be a quick one and required discussion, minimum job price soon after being hired, IP address issue in the middle, Christmas break). I'm leaning towards paying the full amount and calling this an edge case. @0xmiroslav and @rushatgabhane can you please accept the job and reply here once you have? |
This comment was marked as outdated.
This comment was marked as outdated.
@mallenexpensify wait. im not eligible for payment (I was OOO #13523 (comment)) @thesahindia reviewed the PR for this issue #13523 (comment) |
Thanks @rushatgabhane, ended your contract. @thesahindia can you please accept the job and reply here once you have? |
Accepted, thanks! |
@thesahindia paid. @greg-schroeder or I need to add the regression test steps then we'll be done. |
Working on regression test steps now (getting help from Sheena) |
Regression check here: https://expensify.slack.com/archives/C01SKUP7QR0/p1675081857853569 |
File issue to update TestRail w/ new test: https://github.com/Expensify/Expensify/issues/258910 This issue is done now |
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:
The input field should be visible immediately
Actual Result:
The input field is initially missing
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.2.15.2
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Recording.2370.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: