Repository navigation
[Due for payment 2026-07-23] [$250] Start & End date does not matches Title format with Trip-based Auto-reporting #74268
Description
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: v9.2.44-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #70615
Email or phone of affected tester (no customers): applausetester+ndk65@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Windows 11 Home/Chrome
App Component: Workspace Settings
Action Performed:
Preconditions: Ensure you have the beta enabled in OldDot staging:
- Sign in to staging.expensify.com/inbox
- Open JS console and run: SSetNameValuePair('useCustomReportNamesNewExpensify', 'true');
- Reload and verify: g_account.nameValuePairs.useCustomReportNamesNewExpensify; returns 'true'
Open NewDot, navigate to Workspace - Set auto-reporting frequency to By trip;
- Set report title to: Trip from {report:autoreporting:start:MMM dd} to {report:autoreporting:end:MMM dd, yyyy}
- Open https://staging.new.expensify.com/
- Create an expense with Date is 1 Nov, 2025 (not today)
- Create another expense with Date is today
Expected Result:
Start date matches the oldest expense date
End date matches the current date (or most recent expense)
Actual Result:
At step 2 and step 3, Start date and and end date do not matches with the format.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
Bug6994533_1762317959153.Report_name_for_TRip_is_not_correct_as_formula.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021993127171847398014
- Upwork Job ID: 1993127171847398014
- Last Price Increase: 2025-11-25
Activity
melvin-bot commentedon Nov 5, 2025
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.mitarachim commentedon Nov 5, 2025
This issue is failing QA for Test case 5 in this PR #70615
TaduJR commentedon Nov 7, 2025
cc @allroundexperts
TaduJR commentedon Nov 8, 2025
cc @Valforte
[-]Start & End date does not matches Title format with Trip-based Auto-reporting[/-][+][$250] Start & End date does not matches Title format with Trip-based Auto-reporting[/+]melvin-bot commentedon Nov 25, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021993127171847398014
140 remaining items
melvin-bot commentedon Jul 25, 2026
📣 @TaduJR You have been assigned to this job!
Please apply to the Upwork job and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Once you apply to this job, your Upwork ID will be stored and you will be automatically hired for future jobs!
Keep in mind: Code of Conduct | Contributing 📖
mallenexpensify commentedon Jul 27, 2026
@TaduJR can you please accept the job below? Please reply here and tag me once you have.
If you're not sent an offer in Upwork when you're assigned to an issue, please tag me. If an Upwork job exists, please submit a proposal.
upwork.com/jobs/~022080816779921190514
Assuming $125 cuz there's a regression mentioned above that wasn't addressed before payment was due.
@mananjadhav plz complete the BZ checklist and tag me in a post once you have. Thx
TaduJR commentedon Jul 29, 2026
@mallenexpensify
Offer Accepted
Thanks.
mananjadhav commentedon Jul 31, 2026
BugZero Checklist:
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: Could say like a new feature. I don't see any explicit handling done any previous PR. Needed a change on the BE too.
Link to the comment on the Issue:
[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: NA
[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.
I am not sure if any existing regression test exists, hence recommending one to add.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: https://github.com/Expensify/Expensify/issues/668117
Regression Test Proposal
Precondition:
Preconditions:
SSetNameValuePair('useCustomReportNamesNewExpensify', 'true')Trip from {report:autoreporting:start:MMM dd} to {report:autoreporting:end:MMM dd, yyyy}Test:
Online:
Trip from Jan 01 to Jan 15, 2025(matching actual transaction dates)Offline (optimistic):
4. Go offline (toggle airplane mode or disconnect network)
5. Open an existing report that already has an expense dated Jan 1
6. Create a new expense with date Jan 20
7. Verify the report title immediately updates to
Trip from Jan 01 to Jan 20, 2025(not today's date)New report offline:
8. While still offline, create a new expense in a new report with date Feb 10
9. Verify the report title shows
Trip from Feb 10 to Feb 10, 2025Scan expense regression check:
10. Go to the workspace chat
11. Create an empty report
12. Open the newly created report
13. Add a scan expense
14. Verify the report title does not flash raw formula text like
{report:startdate}while SmartScan is processingDo we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-2d61-ab26-0106-157bda7d4574mananjadhav commentedon Jul 31, 2026
@mallenexpensify I've checked and I feel we should add a regression test. I've updated the checklist.
And can you correct the name in the payout summary here.
melvin-bot commentedon Aug 3, 2026
@TaduJR Huh... This is 4 days overdue. Who can take care of this?
mallenexpensify commentedon Aug 4, 2026
@TaduJR can you please accept the job below? Please reply here and tag me once you have.
@mananjadhav name updated above, apologies (GH sucks)
^ Test case created. Thx
garrettmknight commentedon Aug 4, 2026
$125 approved for @mananjadhav