Skip to content

[Due for payment 2025-03-27] [Change Policy] Expense - Report migration system message shows "undefined" after a restart #58442

Closed

Description

@jponikarchuk

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: 9.1.13-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp #57553
Email or phone of affected tester (no customers): applausetester+kok1@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Account has two workspaces.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Submit an expense.
  4. Go to expense report.
  5. Add /change-workspace to the end of the URL and navigate to it.
  6. Select another workspace.
  7. Go to Settings > Troubleshoot.
  8. Click Clear cache and restart > Reset and refresh.
  9. Go to the same expense report in Step 4 (after changing workspace).

Expected Result:

The system message for report migration should remain the same.

Actual Result:

The system message for report migration changes. It shows "changed the workspace to undefined".

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6770359_1741931081441.change_ws.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @CortneyOfstad

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    on Mar 14, 2025
  2. melvin-bot commented on Mar 14, 2025

    @melvin-bot

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

  3. melvin-bot commented on Mar 14, 2025

    @melvin-bot

    Triggered auto assignment to @CortneyOfstad (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.

  4. melvin-bot commented on Mar 14, 2025

    @melvin-bot

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

  5. github-actions commented on Mar 14, 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. mitarachim commented on Mar 14, 2025

    @mitarachim

    @Beamanator @CortneyOfstad QA team found undefined not translated in spanish , should we create new issue for this case ?

    Image
  7. Beamanator commented on Mar 14, 2025

    @Beamanator
    Contributor

    Good question @mitarachim - no issue needed for the undefined translation because we actually should NOT be showing undefined at all, so in this issue we'll fix both at the same time 🙏

  8. Beamanator commented on Mar 14, 2025

    @Beamanator
    Contributor
  9. 15 remaining items

  10. luacmartins commented on Mar 14, 2025

    @luacmartins
    Contributor

    PR in review

  11. moved this to Second Cohort - CRITICAL in [#whatsnext] #migrateon Mar 18, 2025
  12. luacmartins commented on Mar 18, 2025

    @luacmartins
    Contributor

    This is done and doesn't require payment

  13. moved this from Second Cohort - CRITICAL to Done in [#whatsnext] #migrateon Mar 18, 2025
  14. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Mar 20, 2025
  15. changed the title [-][Change Policy] Expense - Report migration system message shows "undefined" after a restart[/-] [+][Due for payment 2025-03-27] [Change Policy] Expense - Report migration system message shows "undefined" after a restart[/+] on Mar 20, 2025
  16. melvin-bot commented on Mar 20, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  17. melvin-bot commented on Mar 20, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.15-9 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-03-27. 🎊

    For reference, here are some details about the assignees on this issue:

    • @eVoloshchak requires payment through NewDot Manual Requests
    • @rayane-d requires payment through NewDot Manual Requests
  18. melvin-bot commented on Mar 20, 2025

    @melvin-bot

    @eVoloshchak / @rayane-d @CortneyOfstad @eVoloshchak / @rayane-d The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions