-
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
[$500] IOU - When we change category of manual request, a small shake can be seen #29877
Comments
Triggered auto assignment to @muttmuure ( |
Bug0 Triage Checklist (Main S/O)
|
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @neil-marcellini ( |
I'm taking a look now |
I confirmed that it's not reproducible on production, but is on staging. However, it's a very minor bug so IMO we shouldn't block deploy on it. I'll check to see if the deployer agrees. production production.movstaging staging.mov |
@francoisl is the deployer and agrees here (internally) that we can polish this later. I'm removing the blocker and making it external. |
Job added to Upwork: https://www.upwork.com/jobs/~0164196a630a5ccb5f |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @cubuspl42 ( |
Not overdue, waiting for proposals. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
I can not reproduce |
@muttmuure can you double check that and close if needed ^ |
@cubuspl42, @neil-marcellini, @muttmuure Eep! 4 days overdue now. Issues have feelings too... |
Bump @muttmuure |
@cubuspl42 @neil-marcellini @muttmuure this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Remove overdue, I bumped Matt |
Having trouble getting into expensifail.com to test this because 2FA is required |
Still reproducible on staging |
@cubuspl42, @neil-marcellini, @muttmuure Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@cubuspl42 @neil-marcellini @muttmuure this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks! |
@cubuspl42, @neil-marcellini, @muttmuure Eep! 4 days overdue now. Issues have feelings too... |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
A duplicate was opened and has an accepted proposal: #30218 |
@cubuspl42, @neil-marcellini, @muttmuure Eep! 4 days overdue now. Issues have feelings too... |
Closing in favor of the other one |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.3.86-0
Reproducible in staging?: Yes
Reproducible in production?: No
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
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Expected Result:
When we change category of manual request, a small shake must not be seen
Actual Result:
When we change category of manual request, a small shake can be seen
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Android: Native
Android: mWeb Chrome
Bug6241848_1697641007790.category_shaken.1.mp4
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop
20231018_212302.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @muttmuureThe text was updated successfully, but these errors were encountered: