Repository navigation
[$250] Reports - After moving expense and deleting all expenses, table header remains in blank page #62507
Description
Activity
- addedDeployBlockerCashThis issue or pull request should block deploymentThis issue or pull request should block deploymentDailyKSv2KSv2BugSomething is broken. Auto assigns a BugZero manager.Something is broken. Auto assigns a BugZero manager.
on May 21, 2025 Triggered auto assignment to @bfitzexpensify (
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.Triggered auto assignment to @puneetlath (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.💬 A slack conversation has been started in #expensify-open-source
github-actions commented
on May 21, 2025 on May 21, 2025 – with GitHub ActionsContributorMore actions👋 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.
- Find someone who can quickly fix the issue.
- Fix the issue yourself.
@bfitzexpensify 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.
Can see the
move expenseoption btw.- removedDeployBlockerCashThis issue or pull request should block deploymentThis issue or pull request should block deployment
on May 21, 2025 11 remaining items
@alitoshmatov what do you think about my proposal here?
@nkdengineer Thank you for your proposal. Your RCA is correct and solution works. I think we should check reports for empty transactions.
We can go with @nkdengineer 's proposal
C+ reviewed 🎀 👀 🎀
Current assignee @puneetlath is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new.
Hmm, interesting. So if you're in the beta everything works correctly. I'm not sure this is worth doing anything about then, since it'll naturally fix itself shortly when the beta becomes live. What do you think @bfitzexpensify?
I think even though the issue will resolve itself when the beta goes live, we should still consider fixing it now because this bug creates a poor experience for non-beta users right now
I agree we can just wait for that beta to go live - this is a niche flow, and only a display issue, not something that prevents a user taking an action.
@puneetlath @bfitzexpensify I received a C+ review here, and my proposal addresses the bug mentioned in the original post. Since the issue has been marked as external, is there any chance I could be considered for partial compensation for my contribution?
@puneetlath @bfitzexpensify could you please check my comment here?
@nkdengineer this would be eligible for partial payment if you as the contributor were hired - in this case, though your proposal was selected by the C, we didn't proceed with hiring.
Thanks for the reply @bfitzexpensify. I think we still provide payment to the contributor if the proposal is C+ reviewed, we have a similar case as in this issue
50% payment if the contributor wasn't assigned and
The proposal was 🎀👀🎀 by the C+, and
Most of the code used in the fix came from the accepted proposalQuote from here
This case doesn't satisfy the last requirement:
Most of the code used in the fix came from the accepted proposal
In your proposal, you noted that:
Note: If you turn on beta, you will see the report with no expense.
And as we're not doing anything for non-beta users, this means the resolution for this already existed pre-proposal.
Reacted by nkdengineerThat makes sense, thanks @bfitzexpensify
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.48-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught during regression testing, add the test name, ID and link from TestRail: #62270
Email or phone of affected tester (no customers): sjdiodjsodsj232@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.4 / Chrome
App Component: Search
Action Performed:
Expected Result:
Table header will disappear.
Empty state will show up.
Actual Result:
Table header does not disappear.
Empty state does not show up.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6838556_1747855043695.20250522_030739.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @