-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[Due for payment 2025-04-16] [Better Expense Report View] button is not disabled when the carousel is at the end of the expense preview #59466
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
Comments
Triggered auto assignment to @laurenreidexpensify ( |
I can just fix it in the desired follow-up: #59452, WDYT @allgandalf @mountiny ? |
@Guccio163 I think its fine to just keep these individual issues open, it makes it easier to track |
@Guccio163 Eep! 4 days overdue now. Issues have feelings too... |
PR merged, no need for payment or regression test at this point (will be added as part of the project) |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.24-10 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 2025-04-16. 🎊 For reference, here are some details about the assignees on this issue:
|
@allgandalf @laurenreidexpensify @allgandalf The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
Uh oh!
There was an error while loading. Please reload this page.
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.1.22-0
Reproducible in staging?: Y
Reproducible in production?: No, New feature
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: #58479
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause - Internal Team
Action Performed:
Precondition:
Expected Result:
Actual Result:
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6789035_1743523360118.20250401_235953.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @laurenreidexpensifyThe text was updated successfully, but these errors were encountered: