-
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
No errors shown when edit amount/date of scanned receipt #48147
Comments
Triggered auto assignment to @CortneyOfstad ( |
We think that this bug might be related to #wave-collect - Release 1 |
@CortneyOfstad FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
📣 @HeinousAgenda38! 📣
|
📣 @Dnts1! 📣
|
This is not a bug from what I see. I have not come across any reference where we provide an error or violation in new dot when first creating/editing an unsubmitted expense, as the message itself is notification/error/violation that the amount and date have been changed on the expense. When the receipt is submitted, we show a violation to notify the admin/approver, but not at this stage. Closing! |
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: v9.0.25-2
Reproducible in staging?: Y
Reproducible in production?: Y
Issue was found when executing this PR: #47607
Issue reported by: Applause Internal Team
Action Performed:
Precondition: user is logged in desktop app.
Expected Result:
After steps 4 and 5, RBR on the money request report/thread appears.
The error message below edited field is shown.
Actual Result:
RBR on the money request report/thread appears in LHN.
No error messages below edited field is shown.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6584080_1724759026227.receipt_change.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: