Skip to content

[Due for payment 2026-07-07] Home - Date cell does not show complete date with year when expense is not from 2026 #94251

Closed

Description

@applause-bot

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.4.17-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: #93451
Email or phone of affected tester (no customers): sdjnoisdjdosijsonssjo@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Create an expense with date that is not from 2026.
  1. Go to staging.new.expensify.com
  2. Go to Home.

Expected Result:

Date cell will show the complete date (with year) when expense date is not from 2026.

Actual Result:

Date cell does not show complete date with year when expense date is not from 2026.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7188082_1782171178962.10.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7188082

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. applause-bot commented on Jun 23, 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/cb5266f612d575d4acb4e45ea09fae3159b3072a1540d3b77bab01753edaf48c

  2. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 23, 2026
  3. melvin-bot commented on Jun 23, 2026

    @melvin-bot

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

  4. melvin-bot commented on Jun 23, 2026

    @melvin-bot

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

  5. github-actions commented on Jun 23, 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. MelvinBot commented on Jun 23, 2026

    @MelvinBot
    Contributor

    Proposal

    What is the root cause of that problem?

    The Home page's "Recently Added" section formats the date cell with a fixed format that has no year. In RecentlyAddedRow.tsx:44:

    const formattedDate = DateUtils.formatWithUTCTimeZone(expense.created, CONST.DATE.MONTH_DAY_ABBR_FORMAT);

    MONTH_DAY_ABBR_FORMAT is 'MMM d' (CONST/index.ts:619) — no year — so any expense dated outside the current year shows e.g. Mar 15 instead of Mar 15, 2025.

    Everywhere else in the app that renders a transaction date, the format is chosen conditionally based on whether the date is in a past year, e.g. SearchList/ListItem/DateCell.tsx:27 and TransactionPreviewUtils.ts:314. This new component, added in #93451, omitted that conditional.

    What changes do you think we should make in order to solve the problem?

    Apply the same past-year check the rest of the codebase uses. In RecentlyAddedRow.tsx:44, pick the year-bearing format when the expense date is from a past year:

    • Use DateUtils.doesDateBelongToAPastYear(expense.created) (DateUtils.ts:864) to choose between CONST.DATE.MONTH_DAY_YEAR_ABBR_FORMAT ('MMM d, yyyy') for past-year dates and CONST.DATE.MONTH_DAY_ABBR_FORMAT ('MMM d') otherwise — identical to the existing DateCell pattern.
    Why this matches the rest of the app

    The exact doesDateBelongToAPastYear(...) ? MONTH_DAY_YEAR_ABBR_FORMAT : MONTH_DAY_ABBR_FORMAT pattern already appears in Search/SearchList/ListItem/DateCell.tsx, ExpenseReportListItemRowNarrow.tsx, WithdrawalIDListItemHeader.tsx, TransactionPreviewUtils.ts, AuthorizeCardTransactionPreview.tsx, and SplitExpensePage.tsx. The Recently Added row is the only date cell that doesn't do this, which is consistent with this being a new-feature regression rather than a broader date bug.

    Note: the DATE_COLUMN_WIDTH = 72 (RecentlyAddedRow.tsx:20) column may be tight for the longer MMM d, yyyy string — worth a quick visual check that it doesn't truncate.

    What alternative solutions did you explore? (Optional)

    None needed — this is a one-line conditional that brings the new component in line with the established convention.


    Next Steps for Contributor+ team:
    To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/94251) to create a draft PR.
    To refine: @MelvinBot <your feedback>
    To reject: Explain why you are rejecting Melvin's proposal.

  7. 7 remaining items

  8. melvin-bot commented on Jun 30, 2026

    @melvin-bot

    @ZhenjaHorbach Still overdue 6 days?! Let's take care of this!

  9. melvin-bot commented on Jul 2, 2026

    @melvin-bot

    @ZhenjaHorbach 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

  10. melvin-bot commented on Jul 3, 2026

    @melvin-bot

    @ZhenjaHorbach Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

  11. melvin-bot commented on Jul 3, 2026

    @melvin-bot

    @ZhenjaHorbach Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

  12. ZhenjaHorbach commented on Jul 3, 2026

    @ZhenjaHorbach
    Contributor

    @grgia
    Let's close this!

  13. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jul 3, 2026
  14. melvin-bot commented on Jul 6, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  15. melvin-bot commented on Jul 6, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  16. ZhenjaHorbach commented on Jul 7, 2026

    @ZhenjaHorbach
    Contributor

    @grgia Let's close this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions