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:
Reproducible in staging?:
Reproducible in production?:
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:
Slack conversation (hyperlinked to channel name): https://expensify.slack.com/archives/C05LX9D6E07/p1747855421259419
Action Performed:
Break down in numbered steps
Not sure but maybe these steps could help:
- As Alice, create a workspace with approvals set up
- Add a another member Bob to the workspace
- Add Carl to the workspace and set him as an approver of Bob
- As Bob, submit 3 expenses to the workspace
- As Alice, copilot into Carl account
- Approve the report from Bob on behalf of Carl
Expected Result:
Describe what you think should've happened
When Bob now goes to the unread expense report, it would get marked as read
Actual Result:
Describe what actually happened
The report is never marked as read by just visiting it
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Select the officially supported platforms where the issue was reproduced:
Platforms Tested:
On which of our officially supported platforms was this issue tested:
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021925478167796105068
- Upwork Job ID: 1925478167796105068
- Last Price Increase: 2025-05-22
Issue Owner
Current Issue Owner: @jliexpensify
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:
Reproducible in staging?:
Reproducible in production?:
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:
Slack conversation (hyperlinked to channel name): https://expensify.slack.com/archives/C05LX9D6E07/p1747855421259419
Action Performed:
Break down in numbered steps
Not sure but maybe these steps could help:
Expected Result:
Describe what you think should've happened
When Bob now goes to the unread expense report, it would get marked as read
Actual Result:
Describe what actually happened
The report is never marked as read by just visiting it
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Select the officially supported platforms where the issue was reproduced:
Platforms Tested:
On which of our officially supported platforms was this issue tested:Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @jliexpensify