Skip to content

[$250] Reports - New expense is not highlighted in Expenses tab when there is at least an expense #62711

Closed

Description

@mitarachim

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.1.51-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): sjdoinsdjosd2oi1@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.4 / Chrome
App Component: Search

Action Performed:

  1. Go to staging.new.expensify.com
  2. Log in with a new account (no expenses).
  3. Go to Reports.
  4. Go to Reports under Explore.
  5. Click FAB > Create expense > Manual.
  6. Submit an expense to any user.
  7. Note that the new expense is auto displayed in Expenses tab.
  8. Go to Reports under Explore.
  9. Click FAB > Create expense > Manual.
  10. Submit an expense to the same user again.

Expected Result:

The new expense row will be temporarily highlighted in Expenses tab.

Actual Result:

The new expense row is not temporarily highlighted in Expenses tab when there is at least an expense.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6840749_1748040587217.20250524_064432.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021929671627279155113
  • Upwork Job ID: 1929671627279155113
  • Last Price Increase: 2025-06-23
Issue OwnerCurrent Issue Owner: @

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 May 24, 2025
  2. melvin-bot commented on May 24, 2025

    @melvin-bot

    Triggered auto assignment to @trjExpensify (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 May 24, 2025

    @melvin-bot

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

  4. melvin-bot commented on May 24, 2025

    @melvin-bot

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

  5. github-actions commented on May 24, 2025

    @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.
  6. removed
    DeployBlockerIndicates it should block deploying the API
    on May 26, 2025
  7. 31 remaining items

  8. mollfpr commented on Jun 16, 2025

    @mollfpr
    Contributor

    Still no takers.

  9. melvin-bot commented on Jun 16, 2025

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  10. melvin-bot commented on Jun 20, 2025

    @melvin-bot

    @trjExpensify, @mollfpr, @ikevin127 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  11. mvtglobally commented on Jun 21, 2025

    @mvtglobally

    Issue not reproducible during KI retests. (First week)

  12. melvin-bot commented on Jun 21, 2025

    @melvin-bot

    @trjExpensify @mollfpr @ikevin127 this issue is now 4 weeks old, please consider:

    • Finding a contributor to fix the bug
    • Closing the issue if BZ has been unable to add the issue to a VIP or Wave project
    • If you have any questions, don't hesitate to start a discussion in #expensify-open-source

    Thanks!

  13. melvin-bot commented on Jun 23, 2025

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  14. mollfpr commented on Jun 23, 2025

    @mollfpr
    Contributor

    Asking for a retest!

  15. IuliiaHerets commented on Jun 23, 2025

    @IuliiaHerets

    @mollfpr Issue is not reproducible on Windows 11/ Chrome in v 9.1.70-3

    bandicam.2025-06-23.23-53-50-117.mp4
  16. mollfpr commented on Jun 25, 2025

    @mollfpr
    Contributor

    It seems fixed somewhere else. Closing!

  17. moved this from Bugs and Follow Up Issues to Done in #expensify-bugson Jun 25, 2025
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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions