-
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
[Search v1.2] - No approve button on the transaction in search page #53018
Comments
Triggered auto assignment to @VictoriaExpensify ( |
This is a BE bug. The BE returns a incorrect value for the isFromOneTransactionReport field Lines 269 to 271 in 3ebe852
As a result, this condition is met, and the View action is displayed. |
Thanks! I'll take a look at it |
Hm this is expected. If the report has multiple expenses, we only show the |
Closing |
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.0.66-0
Reproducible in staging?: Y
Reproducible in production?: Y
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: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause - Internal Team
Issue found when executing PR #52441
Action Performed:
Pre conditions: Make sure you have a report that can be approved, i.e. create a workspace, invite a member, turn on approvals and reimbursement (workflows), as the member submit a few expenses
Expected Result:
Approve button appears next to the expense/report
Actual Result:
No approve buttons are appearing next to the expense/report
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6674002_1732356682180.bandicam_2024-11-23_13-05-40-412.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @luacmartinsIssue Owner
Current Issue Owner: @luacmartinsThe text was updated successfully, but these errors were encountered: