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
Set Expiry Options start date does not default to today's date when expiration is enabled #85268
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: New requirement
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Create flow
Go to Workspace > Expensify Cards > Issue new card.
Select a virtual card and continue to Set Expiry Options (Screen 4).
Toggle Set expiry date on.
Verify that the start date is auto-filled as today
Edit flow
Go to Workspace > Expensify Cards
Click on a virtual card that doesn't set the expired date
Click on Limit type
Toggle Set expiry date on.
Verify that the start date is auto-filled as today
Activity
lakchote commentedon Mar 13, 2026
cc @nkdengineer can you handle it please?
nkdengineer commentedon Mar 14, 2026
@lakchote I can do this
nkdengineer commentedon Mar 16, 2026
@lakchote Please assign me here.
nkdengineer commentedon Mar 16, 2026
@dukenv0307 The PR is ready for review.
nkdengineer commentedon Mar 31, 2026
@mallenexpensify The PR was deployed to production 2 weeks ago. This is ready for payment.
melvin-bot commentedon Apr 2, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)mallenexpensify commentedon Apr 2, 2026
Payment Summary
Contributor: @nkdengineer due $250 via NewDot
Contributor+: @dukenv0307 due $250 via NewDot
@dukenv0307 plz complete the BZ checklist and tag me in a post once you have. Thx
dukenv0307 commentedon Apr 2, 2026
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: New requirement
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-9e38-a48b-66e4-b79bf5e8cdf4dukenv0307 commentedon Apr 2, 2026
@mallenexpensify I completed. Thank you
quinthar commentedon Apr 4, 2026
Approved $250 to @dukenv0307
twisterdotcom commentedon Apr 22, 2026
@nkdengineer has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-074c-aac5-ba15-e7f39bdcbb04