Skip to content

[$250] Reports - First expense row is highlighted each time coming from other status to All #61299

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.39-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): sdnhishsiuds2@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Search

Action Performed:

  1. Go to staging.new.expensify.com
  2. Log in with a new account.
  3. Create a new workspace.
  4. Go to workspace chat.
  5. Submit two expenses.
  6. Go to Reports.
  7. Go to Unreported status.
  8. Go back to All status.
  9. Note that the first expense row is briefly highlighted.
  10. Delete the first expense row.
  11. Go to Unreported status.
  12. Go back to All status.
  13. Note that the first expense row is briefly highlighted.

Expected Result:

When switching from other status to All, the first expense row will not be highlighted.

Actual Result:

Each time switching from other status to All, the first expense row is briefly highlighted.

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

Bug6819231_1746163778995.20250502_132529.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021918251917505708038
  • Upwork Job ID: 1918251917505708038
  • Last Price Increase: 2025-05-09
Issue OwnerCurrent Issue Owner: @jjcoffee

Activity

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

    @melvin-bot

    Triggered auto assignment to @OfstadC (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 2, 2025

    @melvin-bot

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

  4. melvin-bot commented on May 2, 2025

    @melvin-bot

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

  5. github-actions commented on May 2, 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
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on May 2, 2025
  7. 11 remaining items

  8. huult commented on May 3, 2025

    @huult
    Contributor

    as this comment, Is this issue open for proposal?

  9. jjcoffee commented on May 5, 2025

    @jjcoffee
    Contributor

    Thanks @gijoe0295! Looks pretty likely that it's a regression from #60896. cc @martasudol @c3024 to take a look.

  10. melvin-bot commented on May 8, 2025

    @melvin-bot

    @jjcoffee Whoops! This issue is 2 days overdue. Let's get this updated quick!

  11. jjcoffee commented on May 8, 2025

    @jjcoffee
    Contributor

    @martasudol Is there a PR being worked on to fix this issue?

  12. martasudol commented on May 8, 2025

    @martasudol
    Contributor

    #60896 has been reverted so this issue should not occur anymore.

  13. jjcoffee commented on May 8, 2025

    @jjcoffee
    Contributor

    Gotcha, thanks! I guess we can close this then @OfstadC.

  14. melvin-bot commented on May 9, 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? 💸

  15. melvin-bot commented on May 14, 2025

    @melvin-bot

    @jjcoffee Huh... This is 4 days overdue. Who can take care of this?

  16. jjcoffee commented on May 14, 2025

    @jjcoffee
    Contributor

    @OfstadC Bump on this comment.

  17. OfstadC commented on May 15, 2025

    @OfstadC
    Contributor

    Sorry I missed your note @jjcoffee - Closing now

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

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions