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 - There is no Duplicate confirmation modal #69061
Version Number: 9.1.98-0 Reproducible in staging?: Y 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+gm1038139@applause.expensifail.com Issue reported by: Applause - Internal Team
Action Performed:
Create workspace
Go to Workspaces list
Click on 3 dots on workspace
Click on Duplicate workspace
Click Next
Click Duplicate
Expected Result:
Confirmation modal "Duplicate and share workspace ?" should appear, with options Proceed and Cancel to select
Actual Result:
Confirmation modal "Duplicate and share workspace ?" does not appear
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug6924177_1755888267012.Recording__5979.mp4
👋 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.
Culprit PR was reverted. @stitesExpensify should we keep this issue open or not necessary considering there'll be I imagine quite some retesting with the next PR?
Confirmation modal should be shown only if Workspace has members. In the current case if we check here there are no members in the workspace (no members row to select):
Activity
melvin-bot commentedon Aug 22, 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 22, 2025
Triggered auto assignment to @carlosmiceli (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.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
💬 A slack conversation has been started in #expensify-open-source
carlosmiceli commentedon Aug 22, 2025
Culprit PR was reverted. @stitesExpensify should we keep this issue open or not necessary considering there'll be I imagine quite some retesting with the next PR?
stitesExpensify commentedon Aug 22, 2025
I think we can close
narefyev91 commentedon Aug 26, 2025
Confirmation modal should be shown only if Workspace has members. In the current case if we check here there are no members in the workspace (no members row to select):
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.