-
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
Search - Expenses created on a control WS are not showing up on Search page #51270
Comments
Triggered auto assignment to @muttmuure ( |
Triggered auto assignment to @arosiclair ( |
💬 A slack conversation has been started in #expensify-open-source |
We think that this bug might be related to #wave-control |
👋 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:
|
This is expected. Only expenses on migrated policies, i.e. with |
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.52-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: #49412
Email or phone of affected tester (no customers): nathanmulugetatesting+1897@gmail.com
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
The expense created on the Control workspace gets shown on the search page and on step 5 when clicking on FAB the new workspace button does not appear since the user already created a workspace.
Actual Result:
The expense created on the control workspace doesn't get shown on the search page, when clicking FAB the user is shown create a new workspace button even if user already created a control workspace on OD.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6642178_1729610255590.bandicam_2024-10-22_18-05-58-783.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: