App: [$500] RBR doesn't show up on LHN and Report/Expense preview when there is violation(s) with the expense report.
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.4.46-0 Reproducible in staging?: y Reproducible in production?: y 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: @hayata-suenaga Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1709230047147289
Action Performed:
- As A, create a new control workspace on Old Expensify
- Run the script to access the workspace in ND
p = Policy.getCurrent(); p.policy.isPolicyExpenseChatEnabled = "true"; p.save(); - Configure some violations to require Category/tag
- Invite user B as employee and user C as Approver
- Sign in as user B in ND and create an expense report in the workspace created in step 1
- Submit the report to approver
- Sign in as user C in ND
- Look at the LHN and see if there is any violation RBRfor the money request sent by user B
- Open the expense details and see if there is any violation RBR appears
Expected Result:
RBR should be displayed in the LHN and expense details
Actual Result:
RBR doesn’t show up on LHN and Report/Expense preview when there is violation(s) with the expense report
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/38435837/220bc93c-8642-4046-84a1-63c19f33adbb
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~0135cc12979416295b
- Upwork Job ID: 1767297509513805824
- Last Price Increase: 2024-03-18
About this issue
- Original URL
- State: closed
- Created 4 months ago
- Comments: 18 (9 by maintainers)
Looking for more proposals.
Backend bug