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-05-18] [$250] Datepicker - Year is not found if any year prior to 2005 is entered in the search #87455
Version Number: 9.3.55-0 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from BrowserStack:#85107 Email or phone of affected tester (no customers):fischer9966+053122@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: MacOS 26.4 / Chrome, Safari. Google Pixel 5 / Android 14 App Component: Search
Action Performed:
Open Expensify App or go to staging.new.expensify.com
Login with any account
Click "+" > Create expense
Input any amount > Next
Select Date
Click on Year to open year list
Enter any full year prior to 2005 in search field. Eq 2000
Expected Result:
Entered year appeared in search result
Actual Result:
No results found if a year prior to 2005 is entered in full in the search field.
changed the title [-]Datepicker - Year is not found if any year prior to 2005 is entered in the search[/-][+][$250] Datepicker - Year is not found if any year prior to 2005 is entered in the search[/+]on Apr 10, 2026
The expense date picker (IOURequestStepDate.tsx:153) passes CONST.CALENDAR_PICKER.MIN_DATE as the minDate prop, which is defined as dateSubtract(new Date(), {years: 20}) (CONST/index.ts:54). This means the year list in CalendarPicker/index.tsx:105-112 is only populated with years from ~2006 to ~2027.
When a user searches for "2000" (or any year outside this range) in YearPickerModal.tsx:35, the filter years.filter((year) => year.text?.includes(searchText)) correctly returns no matches because those years were never in the list to begin with.
What changes do you think we should make in order to solve the problem?
Change CONST.CALENDAR_PICKER.MIN_DATE in src/CONST/index.ts:54 from 20 years to a larger value (e.g., 100 years to match MIN_YEAR), so the year list includes older years. This single change would fix both the year search and the ability to select older dates across all date pickers that use this constant.
Alternatively, if the 20-year limit is intentional for most contexts, update only IOURequestStepDate.tsx:153 to use a wider minDate (e.g., setYear(new Date(), CONST.CALENDAR_PICKER.MIN_YEAR)) so that the expense date picker specifically allows older dates while other pickers retain the current constraint.
What alternative solutions did you explore? (Optional)
Considered improving the search UX (e.g., showing "Year not available" instead of "No results found"), but that would just paper over the real issue — users legitimately need to select older dates for expenses.
Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.
Activity
mountiny commentedon Apr 10, 2026
@jponikarchuk Why is this labelled as Monthly and Not a priority?
melvin-bot commentedon Apr 10, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ChavdaSachin (
External)[-]Datepicker - Year is not found if any year prior to 2005 is entered in the search[/-][+][$250] Datepicker - Year is not found if any year prior to 2005 is entered in the search[/+]melvin-bot commentedon Apr 10, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022042453113426418208
MelvinBot commentedon Apr 10, 2026
Proposal
What is the root cause of that problem?
The expense date picker (
IOURequestStepDate.tsx:153) passesCONST.CALENDAR_PICKER.MIN_DATEas theminDateprop, which is defined asdateSubtract(new Date(), {years: 20})(CONST/index.ts:54). This means the year list inCalendarPicker/index.tsx:105-112is only populated with years from ~2006 to ~2027.When a user searches for "2000" (or any year outside this range) in
YearPickerModal.tsx:35, the filteryears.filter((year) => year.text?.includes(searchText))correctly returns no matches because those years were never in the list to begin with.What changes do you think we should make in order to solve the problem?
Change
CONST.CALENDAR_PICKER.MIN_DATEinsrc/CONST/index.ts:54from 20 years to a larger value (e.g., 100 years to matchMIN_YEAR), so the year list includes older years. This single change would fix both the year search and the ability to select older dates across all date pickers that use this constant.Alternatively, if the 20-year limit is intentional for most contexts, update only
IOURequestStepDate.tsx:153to use a widerminDate(e.g.,setYear(new Date(), CONST.CALENDAR_PICKER.MIN_YEAR)) so that the expense date picker specifically allows older dates while other pickers retain the current constraint.What alternative solutions did you explore? (Optional)
Considered improving the search UX (e.g., showing "Year not available" instead of "No results found"), but that would just paper over the real issue — users legitimately need to select older dates for expenses.
Next Steps for Contributor+ team: Reply with
@MelvinBot implement thisto create a draft PR,@MelvinBot <your feedback>to refine this analysis, or explain why you are rejecting Melvin's proposal.42 remaining items
melvin-bot commentedon May 17, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon May 18, 2026
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
melvin-bot commentedon May 20, 2026
@mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon May 22, 2026
@mallenexpensify Eep! 4 days overdue now. Issues have feelings too...
mallenexpensify commentedon May 26, 2026
Payment Summary
Contributor+: @ChavdaSachin due $250 via NewDot
^ Test case created. Thx
quinthar commentedon May 30, 2026
Approved $250 to @ChavdaSachin