You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug was found when validating #40153 Version Number: 1.4.81-8 Reproducible in staging?: y 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:
. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Submit two scan expenses with the same receipt (so that they will be flagged as duplicate).
4. Wait for both scanning to complete.
5. Go to expense report (make sure both expenses have the "Duplicate" label)
6. Go to transaction thread of one of the expenses.
7. Change the amount so that both expenses are no longer duplicate.
8. Return to expense report.
Expected Result:
The edited expense will not have "Review required" label, if there is no error message or violation in the transaction thread.
Actual Result:
The edited expense shows "Review required" label, but there is no error message or violation in the transaction thread.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Bug was found when validating #40153
Version Number: 1.4.81-8
Reproducible in staging?: y
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:
. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Submit two scan expenses with the same receipt (so that they will be flagged as duplicate).
4. Wait for both scanning to complete.
5. Go to expense report (make sure both expenses have the "Duplicate" label)
6. Go to transaction thread of one of the expenses.
7. Change the amount so that both expenses are no longer duplicate.
8. Return to expense report.
Expected Result:
The edited expense will not have "Review required" label, if there is no error message or violation in the transaction thread.
Actual Result:
The edited expense shows "Review required" label, but there is no error message or violation in the transaction thread.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6509423_1718114254702.20240611_213817.mp4
View all open jobs on GitHub