You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Search - Expenses created on a control WS are not showing up on Search page #51270
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:
Navigate to staging.expensify.com/inbox
Create a new Gmail account
Create a control workspace
Click on concierge to navigate to newDot
Click on FAB > Submit expense > Enter an amount > Select the control workspace created in OD and finish the creation flow
Go to search page
For comparison create a new workspace and submit an expense on the newly created workspace and go to search page
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
Activity
melvin-bot commentedon Oct 22, 2024
Triggered auto assignment to @muttmuure (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Oct 22, 2024
Triggered auto assignment to @arosiclair (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 22, 2024
💬 A slack conversation has been started in #expensify-open-source
IuliiaHerets commentedon Oct 22, 2024
We think that this bug might be related to #wave-control
github-actions commentedon Oct 22, 2024
👋 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:
luacmartins commentedon Oct 22, 2024
This is expected. Only expenses on migrated policies, i.e. with
policyExpenseChatEnabledset to true should show up.