You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-07-07] Home - Date cell does not show complete date with year when expense is not from 2026 #94251
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.
Go to staging.new.expensify.com
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.
👋 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.
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.
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.
Activity
applause-bot commentedon Jun 23, 2026
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
melvin-bot commentedon Jun 23, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #93451
melvin-bot commentedon Jun 23, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jun 23, 2026
👋 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:
MelvinBot commentedon Jun 23, 2026
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:MONTH_DAY_ABBR_FORMATis'MMM d'(CONST/index.ts:619) — no year — so any expense dated outside the current year shows e.g.Mar 15instead ofMar 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:27andTransactionPreviewUtils.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:DateUtils.doesDateBelongToAPastYear(expense.created)(DateUtils.ts:864) to choose betweenCONST.DATE.MONTH_DAY_YEAR_ABBR_FORMAT('MMM d, yyyy') for past-year dates andCONST.DATE.MONTH_DAY_ABBR_FORMAT('MMM d') otherwise — identical to the existingDateCellpattern.Why this matches the rest of the app
The exact
doesDateBelongToAPastYear(...) ? MONTH_DAY_YEAR_ABBR_FORMAT : MONTH_DAY_ABBR_FORMATpattern already appears inSearch/SearchList/ListItem/DateCell.tsx,ExpenseReportListItemRowNarrow.tsx,WithdrawalIDListItemHeader.tsx,TransactionPreviewUtils.ts,AuthorizeCardTransactionPreview.tsx, andSplitExpensePage.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 longerMMM d, yyyystring — 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 remaining items
melvin-bot commentedon Jun 30, 2026
@ZhenjaHorbach Still overdue 6 days?! Let's take care of this!
melvin-bot commentedon Jul 2, 2026
@ZhenjaHorbach 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!
melvin-bot commentedon Jul 3, 2026
@ZhenjaHorbach Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!
melvin-bot commentedon Jul 3, 2026
@ZhenjaHorbach Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!
ZhenjaHorbach commentedon Jul 3, 2026
@grgia
Let's close this!
melvin-bot commentedon Jul 6, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Jul 6, 2026
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
ZhenjaHorbach commentedon Jul 7, 2026