Skip to content

[Insights] Reports-Expense on Sunday is not displayed in groupby list #80846

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.3.11-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: #80684
Email or phone of affected tester (no customers): ndk.2303+224@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Windows 11 Home/Chrome
App Component: Search

Action Performed:

  1. Open https://staging.new.expensify.com/
  2. Create an expense (Date: on a Sunday of a week that has not any expense; ex: 7 Sep, 2025)
  3. Navigate to Reports
  4. Go to Expense section
  5. Click on Filter
  6. Click on 'Group by' section
  7. Select 'Week' and view result
  8. Expand the week group that contains the expense

Expected Result:

Expense should be shown on the list of group

Actual Result:

The date of expense (Sep 7, 2025) is grouped in the previous week group (Aug 31 - Sep 6, 2025).
When the row is expanded, the expense is not displayed.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7060819_1769654599148.Sunday_expense_not_shown.mp4
Bug7060819_1769654451891.Sunday_expense_is_misssing.mp4

View all open jobs on GitHub

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 Jan 29, 2026
  2. melvin-bot commented on Jan 29, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #80684

  3. melvin-bot commented on Jan 29, 2026

    @melvin-bot

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

  4. melvin-bot commented on Jan 29, 2026

    @melvin-bot

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

  5. github-actions commented on Jan 29, 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. shubham1206agra commented on Jan 29, 2026

    @shubham1206agra
    Contributor

    @neil-marcellini @cristipaval @lakchote Another BE issue as I can see the query is correct from FE

  7. 6 remaining items

  8. lakchote commented on Jan 29, 2026

    @lakchote
    Contributor
  9. self-assigned this
    on Jan 29, 2026
  10. cristipaval commented on Jan 29, 2026

    @cristipaval
    Contributor

    I suspect the front-end is the culprit here, because the backend counts the expense in the group (you can see in the screen recording that the expense count is 1). But the front-end passes bad dates to the backend when the user pulls the expenses from the group

  11. lakchote commented on Jan 30, 2026

    @lakchote
    Contributor

    I suspect the front-end is the culprit here, because the backend counts the expense in the group (you can see in the screen recording that the expense count is 1). But the front-end passes bad dates to the backend when the user pulls the expenses from the group

    cc @shubham1206agra you said above in #80846 (comment), that the query looked correct?

  12. shubham1206agra commented on Jan 30, 2026

    @shubham1206agra
    Contributor

    @lakchote, I believe the groupBy query is returning incorrect results: it is returning a Sunday date as the group key, but the group count starts from Monday.

  13. lakchote commented on Jan 30, 2026

    @lakchote
    Contributor

    @cristipaval we might want the backend fix I put in https://github.com/Expensify/Auth/pull/19617 that was reverted to have incremental changes

  14. changed the title [-]Reports-Expense on Sunday is not displayed in groupby list[/-] [+][Insights] Reports-Expense on Sunday is not displayed in groupby list[/+] on Jan 30, 2026
  15. cristipaval commented on Feb 2, 2026

    @cristipaval
    Contributor

    On my list for today

  16. trjExpensify commented on Feb 5, 2026

    @trjExpensify
    Contributor

    This was fixed in Auth right, can we close it?

  17. lakchote commented on Feb 6, 2026

    @lakchote
    Contributor

    Correct, closing it.

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.DailyKSv2EngineeringReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions