You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Workspace - Expensify Card tab is present on the duplicated workspace when duplicated offline #69062
Version Number: 9.1.98-0 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:#67412 Email or phone of affected tester (no customers):applausetester+140823kh2h1@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Workspace Settings
Action Performed:
Precondition:
Workspace is set up with Expensify card and has assigned at least one card to any member.
Go to staging.new.expensify.com
Go to workspace list.
Go offline.
Click 3-dot menu on the workspace that has Expensify Card.
Click Duplicate Workspace.
Click Next.
Click Continue.
Go to the duplicated workspace > Expensify Card.
Expected Result:
Expensify Card tab should not be present on the duplicated workspace.
Actual Result:
Expensify Card tab is present on the duplicated workspace when duplicated offline and it shows all the assigned cards.
After returning online, Expensify Card tab disappears.
👋 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:
Identify the pull request that introduced this issue and revert it.
Based on the design doc:
"Expensify Card - We will not show this option, but if it is enabled via “More features” it will be enabled in the new workspace with no feed copied" - i will fix offline mode.
But when user goes back online - Expensify card menu item should be available - we need to check on BE side - why "areExpensifyCardsEnabled" - set to false - if workspace which we try to duplicate has areExpensifyCardsEnabled = true
Activity
melvin-bot commentedon Aug 22, 2025
Triggered auto assignment to @sonialiap (
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.github-actions commentedon Aug 22, 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:
melvin-bot commentedon Aug 22, 2025
Triggered auto assignment to @roryabraham (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Aug 22, 2025
💬 A slack conversation has been started in #expensify-open-source
mountiny commentedon Aug 23, 2025
cc @narefyev91 for visibility #69055
mountiny commentedon Aug 23, 2025
The feature PR was reverted so I think we can close this issue and @narefyev91 can add it to PR v2
narefyev91 commentedon Aug 26, 2025
Based on the design doc:
"Expensify Card - We will not show this option, but if it is enabled via “More features” it will be enabled in the new workspace with no feed copied" - i will fix offline mode.
But when user goes back online - Expensify card menu item should be available - we need to check on BE side - why "areExpensifyCardsEnabled" - set to false - if workspace which we try to duplicate has areExpensifyCardsEnabled = true
mountiny commentedon Aug 26, 2025
Raised a PR with a fix
melvin-bot commentedon Sep 3, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Sep 3, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.