Repository navigation
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.97-1
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 TestRail: #65862
Email or phone of affected tester (no customers): applausetester+ag1908.3@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Windows 11/ Chrome, Samsung S23FE/ Android 15, iPhone 13 Mini/ iOS 18.5
App Component: Money Requests
Action Performed:
- Go to staging.new.expensify.com
- Log in with an Expensifail account
- Create a workspace
- Go to workspace settings > Reports
- Click Default report title
- Edit the Default report title field with:
Report from {report:policyname} - Go offline
- Create a new report via FAB
- Note the current report title
- Go to Workspace settings
- Change workspace name
- Return to the report created in step 8 and verify that the report title has been updated with the new workspace name
- Go online
Expected Result:
The report title remains the same as offline mode. The workspace name matches the update in the workspace settings.
Actual Result:
The report title is changed to the previous workspace name.
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
Bug6921488_1755642830813.Policyname.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021958994231583202611
- Upwork Job ID: 1958994231583202611
- Last Price Increase: 2025-09-18
Issue Owner
Current Issue Owner: @abdulrahuman5196Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
melvin-bot commentedon Aug 20, 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.melvin-bot commentedon Aug 20, 2025
Triggered auto assignment to @Valforte (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Aug 20, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Aug 20, 2025
👋 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:
Valforte commentedon Aug 20, 2025
This is related to #65862
@neil-marcellini can you confirm it's a deploy blocker? I can see the case for this to be an edge case and be demoted but I'm not sure how thorough we want to be with the new report names feature
neil-marcellini commentedon Aug 20, 2025
Not a blocker as explained here
49 remaining items
zanyrenney commentedon Sep 17, 2025
Ah okay @neil-marcellini - thanks for the additional detail.
@mitarachim please can you retest with the steps in the doc provided?
melvin-bot commentedon Sep 17, 2025
@Valforte @abdulrahuman5196 @zanyrenney this issue is now 4 weeks old, please consider:
Thanks!
izarutskaya commentedon Sep 18, 2025
Hi @neil-marcellini Thank you for for the detailed instructions, but could you please clarify? We need to complete
Pre-testing stepsbefore recheck the issue or complete all steps from this document, then double check this issue..mitarachim commentedon Sep 18, 2025
Hello @neil-marcellini @zanyrenney , QA team performed a retest by completing the
Pre-testing stepsas per document and re-tested the issue using the original steps.Issue not reproducible on Windows 11/ Chrome in v9.2.15-11, but the previous workspace name is briefly displayed after going back online.
Repro.68807-2.mp4
melvin-bot commentedon Sep 18, 2025
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
Valforte commentedon Sep 18, 2025
This is a minor bug, in a very fringe case. According to the last comment from @mitarachim do you believe we should still try to fix this or is it good to close @neil-marcellini ?
neil-marcellini commentedon Sep 18, 2025
Let's fix it externally, since it looks like a front end only problem. It's not a blocker for the launch of the backend implementation.
Valforte commentedon Sep 18, 2025
@abdulrahuman5196, can you review the current proposals with the last message from @mitarachim in mind and maybe request an update from the proposal authors?
zanyrenney commentedon Sep 19, 2025
bump @abdulrahuman5196 !
mvtglobally commentedon Sep 20, 2025
Issue not reproducible during KI retests. (First week)
abdulrahuman5196 commentedon Sep 21, 2025
@Valforte / @neil-marcellini
Is this the issue we are trying to solve now? Because QA's have mentioned the original issue is not reproducible.
@LorenzoBloedow Kindly update proposal if required.
zanyrenney commentedon Sep 22, 2025
Closing as per #68807 (comment)