Skip to content

[Due for payment 2026-11-23] Spend - After approving report, result only shows up after reapplying group-by:approver #105557

Open

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.5.27-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #102635
Email or phone of affected tester (no customers): sondjosdjosio@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Search

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense.
  4. Go to Spend > Expenses.
  5. Click Display > Group by > Approver > Apply.
  6. Go back to workspace chat.
  7. Click Submit and Approve on the expense.
  8. Go to Spend > Expenses.
    → No result is returned after submitting and approving report when group by is Approver.
  9. Click Display > Group by > Reset.
  10. Click Display > Group by > Approver > Apply.
    → Result only returns after reapplying group-by:approver.

Expected Result:

After approving report, result will auto show up on group-by:approver view.

Actual Result:

After approving report, result only shows up after reapplying group-by:approver.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7301393_1793458501166.3.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7301393

Issue OwnerCurrent Issue Owner: @nkdengineer

Activity

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

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/4c2be7f5c7a71d37e6f6f74bc889d3007db243b715297ccecb788be8dc7f2266

  3. melvin-bot commented on Oct 31, 2026

    @melvin-bot

    @neil-marcellini recently merged #102635, but they are OOO right now, so I'll auto-assign someone else.

  4. melvin-bot commented on Oct 31, 2026

    @melvin-bot

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

  5. github-actions commented on Oct 31, 2026

    @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. melvin-bot commented on Oct 31, 2026

    @melvin-bot

    @neil-marcellini @daledah you have been assigned to this deploy blocker because you reviewed the offending PR: #102635

  7. melvin-bot commented on Oct 31, 2026

    @melvin-bot

    @nkdengineer you have been assigned to this deploy blocker because you authored the offending PR: #102635

  8. 9 remaining items

  9. melvin-bot commented on Nov 5, 2026

    @melvin-bot

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

  10. nkdengineer commented on Nov 6, 2026

    @nkdengineer
    Contributor

    @daledah The PR is ready for review.

  11. changed the title [-]Spend - After approving report, result only shows up after reapplying group-by:approver[/-] [+][Due for payment 2026-11-23] Spend - After approving report, result only shows up after reapplying group-by:approver[/+] on Nov 16, 2026
  12. melvin-bot commented on Nov 16, 2026

    @melvin-bot

    @nkdengineer / @daledah

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.39-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-11-23. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

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.DailyKSv2EngineeringOverdue

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions