-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Desktop - Chat - Composer menu still contains "Submit expense" option #54129
Comments
Triggered auto assignment to @mallenexpensify ( |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
Will look into next week, trying to get to the source of where we decided on the change that's listed as the expected behaviour in the OP. SIDE NOTE: I've used |
I can reproduce (same steps as OP) but not sure if this is a bug |
Same @s77rt , will update next week |
It's not a bug. We only cleaned up the FAB for Submit Expense. The rest of the cleanup at other places including the composer will be handled here #54006. @mallenexpensify I think we're good to close this one. |
Thx @mananjadhav , closing |
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.76-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Issue was found when executing this PR: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: #53385
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: macOS Sequoia 15.0
App Component: Chat Report View
Action Performed:
Expected Result:
It should be "Create expense".
Actual Result:
Composer menu still contains "Submit expense" option. FAB displays "Create expense" correctly.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6693772_1734118665388.Screen_Recording_2024-12-13_At_11.31.21.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: