-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invoice - Room name displays the wrong name #41321
Comments
Triggered auto assignment to @flodnv ( |
Triggered auto assignment to @bfitzexpensify ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
@bfitzexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors. |
We think this bug might be related to #wave-collect - Release 1 |
I'll take this one, it is #vip-billpay related |
demoting as it is a minor UI thing |
#vip-billpay related. cc @danielrvidal |
@cristipaval should we close this one in lieu of the below, which is going to remove the room name field in general? |
you're right, we should close this one |
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.68-0
Reproducible in staging?: yes
Reproducible in production?: no, new feature
If this was caught during regression testing, add the test name, ID and link from TestRail: n/a
Email or phone of affected tester (no customers): n/a
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:
Expected Result:
Room name should display 'chat-report'
Actual Result:
Room name displays '#hat report'
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6466526_1714479757162.Screen_Recording_2024-04-30_at_3.13.12_in_the_afternoon.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: