Closed lanitochka17 closed 8 months ago
Updated in production. Display name now works.
https://github.com/Expensify/App/assets/17171674/bdfc0ef7-d749-4c64-a765-574223628c1f
I'm going to do a bit of code cleanup on the frontend, then I will consider this done and close the issue.
@eVoloshchak, @slafortune, @anmurali, @blimpich Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
Ah I forgot to close this issue. Frontend changes have been merged and a separate issue was created for paying the C+ contributor here: https://github.com/Expensify/App/issues/37190.
Since payment is handled in that issue and this issue has been resolved I'm going to close this now.
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.8-1 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: Applause - Internal Team Slack conversation:
Action Performed:
Expected Result:
In Step 4, the owner of "scanning failed" system message is displayed as Expensify
Actual Result:
In Step 4, the owner of "scanning failed" system message is notifications@expensify.com. It only changes to Expensify after opening the system message in thread
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/78819774/67410c2b-baee-47b4-9f79-16ed8c8acaa6
View all open jobs on GitHub
Upwork Automation - Do Not Edit