Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
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: 9.0.64-4
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: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/4856Expensify/Expensify Issue URL:Issue reported by: @twisterdotcom
Slack conversation (hyperlinked to channel name): ts_external_expensify_bugs
Action Performed:
User A and User B have an existing chat
User A adds User C as a copilot. (User C has not interacted with User B)
User C copilots into User A's account and sends a message to User B
Expected Result:
Main name for the message is from User C and message as on behalf of user A
Actual Result:
Main name for the message is from User A on behalf of User A
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!
Version Number: 9.0.64-4 Reproducible in staging?: Y Reproducible in production?: Y If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: 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: @twisterdotcom Slack conversation (hyperlinked to channel name): ts_external_expensify_bugs
Action Performed:
Expected Result:
Main name for the message is from User C and message as on behalf of user A
Actual Result:
Main name for the message is from User A on behalf of User A
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @dangrous