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.85-1
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: No
Email or phone of affected tester (no customers): tom+copilot1@trj.chat
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL: None
Issue reported by: @trjExpensify
Slack conversation: #expense
Action Performed:
- As userA, create a workspace
- As userA, add userB as a workspace member
- As userA, add userB as a copilot
- As userB, toggle into userA's account (Settings > account name (dropdown))
- Go to userA's workspace chat
- Click the + icon > create expense > enter an amount > confirm
- Observe the preview component.
Expected Result:
Note: This is a new feature. It's not clear that the copilot acted on behalf of someone to create the expense. I actually thought it was a bug where we were mixing up chats or something. To improve the clarity, let's:
- Add the "on behalf of <displayName" sub-title to the preview actions (expense report and expense) displayed in the parent chat.
Example:
Actual Result:
We don't include the "on behalf of" sub-title:
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
In-line above.
View all open jobs on GitHub
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021879310056365767460
- Upwork Job ID: 1879310056365767460
- Last Price Increase: 2025-01-21
- Automatic offers:
- truph01 | Contributor | 105794951
Issue Owner
Current Issue Owner: @trjExpensify
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.85-1
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: No
Email or phone of affected tester (no customers): tom+copilot1@trj.chat
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL: None
Issue reported by: @trjExpensify
Slack conversation: #expense
Action Performed:
Expected Result:
Note: This is a new feature. It's not clear that the copilot acted on behalf of someone to create the expense. I actually thought it was a bug where we were mixing up chats or something. To improve the clarity, let's:
Example:
Actual Result:
We don't include the "on behalf of" sub-title:
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
In-line above.
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @trjExpensify