Skip to content

Search - Expenses created on a control WS are not showing up on Search page #51270

Closed

Description

@IuliiaHerets

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:

  1. Navigate to staging.expensify.com/inbox
  2. Create a new Gmail account
  3. Create a control workspace
  4. Click on concierge to navigate to newDot
  5. Click on FAB > Submit expense > Enter an amount > Select the control workspace created in OD and finish the creation flow
  6. Go to search page
  7. 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.

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6642178_1729610255590.bandicam_2024-10-22_18-05-58-783.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 22, 2024
  2. melvin-bot commented on Oct 22, 2024

    @melvin-bot

    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.

  3. melvin-bot commented on Oct 22, 2024

    @melvin-bot

    Triggered auto assignment to @arosiclair (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Oct 22, 2024

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. IuliiaHerets commented on Oct 22, 2024

    @IuliiaHerets
    Author

    We think that this bug might be related to #wave-control

  6. github-actions commented on Oct 22, 2024

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  7. luacmartins commented on Oct 22, 2024

    @luacmartins
    Contributor

    This is expected. Only expenses on migrated policies, i.e. with policyExpenseChatEnabled set to true should show up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringHourlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions