Skip to content

[Search v1] - Deleted expense is not removed from Search #43415

Closed

Description

@m-natarajan

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.81-1
Reproducible in staging?: y
Reproducible in production?: no
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: applause internal team
Slack conversation:

Action Performed:

Precondition:

  • User has many expenses.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Submit an expense.
  4. Go to Search.
  5. Note that the submitted expense is shown.
  6. Go to workspace chat and delete the expense.
  7. Refresh the page.
  8. Go to Search.

Expected Result:

The deleted expense will be removed from Search.

Actual Result:

The deleted expense is not removed from Search.
This issue is not reproducible with new account that doesn't have expenses.

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6508394_1718039647926.bandicam_2024-06-11_01-10-13-030.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @luacmartins

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jun 10, 2024
  2. melvin-bot commented on Jun 10, 2024

    @melvin-bot

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

  3. melvin-bot commented on Jun 10, 2024

    @melvin-bot

    Triggered auto assignment to @puneetlath (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.

  4. github-actions commented on Jun 10, 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.
  5. m-natarajan commented on Jun 10, 2024

    @m-natarajan
    Author

    @puneetlath 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

  6. m-natarajan commented on Jun 10, 2024

    @m-natarajan
    Author

    We think that this bug might be related to #wave-collect - Release 1

  7. luacmartins commented on Jun 10, 2024

    @luacmartins
    Contributor

    This is expected for now.

  8. 55 remaining items

  9. luacmartins commented on Sep 6, 2024

    @luacmartins
    Contributor

    PR in review

  10. melvin-bot commented on Sep 16, 2024

    @melvin-bot

    @luacmartins Eep! 4 days overdue now. Issues have feelings too...

  11. melvin-bot commented on Sep 18, 2024

    @melvin-bot

    @luacmartins 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

  12. melvin-bot commented on Sep 20, 2024

    @melvin-bot

    @luacmartins Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

  13. melvin-bot commented on Sep 24, 2024

    @melvin-bot

    @luacmartins 12 days overdue. Walking. Toward. The. Light...

  14. melvin-bot commented on Sep 27, 2024

    @melvin-bot

    This issue has not been updated in over 14 days. @luacmartins eroding to Weekly issue.

  15. melvin-bot commented on Oct 21, 2024

    @melvin-bot

    This issue has not been updated in over 15 days. @luacmartins eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  16. luacmartins commented on Oct 31, 2024

    @luacmartins
    Contributor

    This is done

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

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringInternalRequires API changes or must be handled by Expensify staffMonthlyKSv2ReviewingHas a PR in review

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions