Skip to content

[$250] Expense-Report title reverts to the previous workspace name when it comes back online #68807

Closed

Description

@mitarachim

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:

  1. Go to staging.new.expensify.com
  2. Log in with an Expensifail account
  3. Create a workspace
  4. Go to workspace settings > Reports
  5. Click Default report title
  6. Edit the Default report title field with:
    Report from {report:policyname}
  7. Go offline
  8. Create a new report via FAB
  9. Note the current report title
  10. Go to Workspace settings
  11. Change workspace name
  12. Return to the report created in step 8 and verify that the report title has been updated with the new workspace name
  13. 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

View all open jobs on GitHub

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 OwnerCurrent Issue Owner: @abdulrahuman5196

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Aug 20, 2025
  2. melvin-bot commented on Aug 20, 2025

    @melvin-bot

    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.

  3. melvin-bot commented on Aug 20, 2025

    @melvin-bot

    Triggered auto assignment to @Valforte (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Aug 20, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Aug 20, 2025

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. Valforte commented on Aug 20, 2025

    @Valforte
    Contributor

    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

  7. neil-marcellini commented on Aug 20, 2025

    @neil-marcellini
    Contributor

    Not a blocker as explained here

  8. 49 remaining items

  9. zanyrenney commented on Sep 17, 2025

    @zanyrenney
    Contributor

    Ah okay @neil-marcellini - thanks for the additional detail.

    @mitarachim please can you retest with the steps in the doc provided?

  10. melvin-bot commented on Sep 17, 2025

    @melvin-bot

    @Valforte @abdulrahuman5196 @zanyrenney this issue is now 4 weeks old, please consider:

    • Finding a contributor to fix the bug
    • Closing the issue if BZ has been unable to add the issue to a VIP or Wave project
    • If you have any questions, don't hesitate to start a discussion in #expensify-open-source

    Thanks!

  11. izarutskaya commented on Sep 18, 2025

    @izarutskaya

    Hi @neil-marcellini Thank you for for the detailed instructions, but could you please clarify? We need to complete Pre-testing steps before recheck the issue or complete all steps from this document, then double check this issue..

  12. mitarachim commented on Sep 18, 2025

    @mitarachim
    Author

    Hello @neil-marcellini @zanyrenney , QA team performed a retest by completing the Pre-testing steps as 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
  13. melvin-bot commented on Sep 18, 2025

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  14. Valforte commented on Sep 18, 2025

    @Valforte
    Contributor

    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 ?

  15. neil-marcellini commented on Sep 18, 2025

    @neil-marcellini
    Contributor

    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.

  16. Valforte commented on Sep 18, 2025

    @Valforte
    Contributor

    @abdulrahuman5196, can you review the current proposals with the last message from @mitarachim in mind and maybe request an update from the proposal authors?

  17. zanyrenney commented on Sep 19, 2025

    @zanyrenney
    Contributor
  18. mvtglobally commented on Sep 20, 2025

    @mvtglobally

    Issue not reproducible during KI retests. (First week)

  19. abdulrahuman5196 commented on Sep 21, 2025

    @abdulrahuman5196
    Contributor

    @Valforte / @neil-marcellini

    but the previous workspace name is briefly displayed after going back online.

    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.

  20. zanyrenney commented on Sep 22, 2025

    @zanyrenney
    Contributor

    Closing as per #68807 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsretest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions