Repository navigation
Closed
Labels
BugSomething is broken. Auto assigns a BugZero manager.Something is broken. Auto assigns a BugZero manager.DailyKSv2KSv2ExternalAdded to denote the issue can be worked on by a contributorAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsApply this label when an issue is open to proposals by contributors
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.1.98-7
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: #68737
Email or phone of affected tester (no customers): applausetester+dp316@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac / Safari
App Component: Other
Action Performed:
- Sign in with an account on OldDot
- Open the JS console and enter this to enable the backend beta SSetNameValuePair('useCustomReportNamesNewExpensify', 'true');
- Go to NewDot
- Go to Workspaces, select your workspace and go to Reports subpage
- Edit Default report title to Report from {report:startdate}
- Create new report and add two transactions
a. first with date 2025-08-16
b. second with date 2025-08-17 - Check if report's name is equal to Report from 2025-08-16
- Go to Account -> Troubleshoot and enable Force offline option
- Go back to newly created report
- Edit second transaction's date to 2025-08-14
- Check if report's name is equal to Report from 2025-08-14
- Turn back transaction's date to 2025-08-17
- Check if report's name is equal to Report from 2025-08-16
- Add new transaction with date 2025-08-05
- Check if report's name is equal to Report from 2025-08-05
Expected Result:
- After changing the second transaction’s date to 2025-08-14, the title should be “Report from 2025-08-14”.
- After reverting the date to 2025-08-17, the title should return to “Report from 2025-08-16”.
- After adding a new transaction with 2025-08-05, the title should update to “Report from 2025-08-05”.
Actual Result:
While offline mode is enabled, the report title does not update after editing transaction dates or adding new ones.
The title remains unchanged until the app goes back online, at which point it updates correctly.
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
Bug6926520_1756148468963.11_51_AM_2025-08-25.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021961144129140396167
- Upwork Job ID: 1961144129140396167
- Last Price Increase: 2025-08-28
Issue Owner
Current Issue Owner: @shubham1206agraMetadata
Metadata
Assignees
Labels
BugSomething is broken. Auto assigns a BugZero manager.Something is broken. Auto assigns a BugZero manager.DailyKSv2KSv2ExternalAdded to denote the issue can be worked on by a contributorAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsApply this label when an issue is open to proposals by contributors
Activity
melvin-bot commentedon Aug 25, 2025
Triggered auto assignment to @zanyrenney (
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.[-]69038 - PR68737 - Report title is not update offline[/-][+][$250] 69038 - PR68737 - Report title is not update offline[/+]melvin-bot commentedon Aug 28, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021961144129140396167
melvin-bot commentedon Aug 28, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @shubham1206agra (
External)shubham1206agra commentedon Aug 29, 2025
@sosek108 Would you like to take this one?
sosek108 commentedon Aug 29, 2025
The original implementation of that functionality was reverted because of deploy blockers. We're working on reintroducing this in #69175.
@shubham1206agra thanks for tagging me
shubham1206agra commentedon Aug 29, 2025
@sosek108 We can close this issue then, right?
sosek108 commentedon Aug 29, 2025
I'm sure that we can close. This exact use case is added to QA steps in my PR here #69147.
It won't be missed
melvin-bot commentedon Sep 1, 2025
@shubham1206agra Whoops! This issue is 2 days overdue. Let's get this updated quick!
zanyrenney commentedon Sep 2, 2025
Closing due to dupe.