Skip to content

[Due for payment 2025-09-19] [Due for payment 2025-09-04] Implement Duplicate Workspace feature #67289

Closed

Description

@MitchExpensify

Issue to be referenced when building the Duplicate Workspace feature

Doc

Issue OwnerCurrent Issue Owner: @sonialiap

Activity

  1. melvin-bot commented on Jul 28, 2025

    @melvin-bot

    Triggered auto assignment to @lydiabarclay (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.

  2. melvin-bot commented on Jul 28, 2025

    @melvin-bot

    ⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️

  3. melvin-bot commented on Jul 28, 2025

    @melvin-bot

    Triggered auto assignment to Design team member for new feature review - @shawnborton (NewFeature)

  4. MitchExpensify commented on Aug 5, 2025

    @MitchExpensify
    ContributorAuthor

    This is being implemented

  5. 46 remaining items

  6. changed the title [-][Due for payment 2025-09-04] Implement Duplicate Workspace feature[/-] [+][Due for payment 2025-09-19] [Due for payment 2025-09-04] Implement Duplicate Workspace feature[/+] on Sep 12, 2025
  7. melvin-bot commented on Sep 12, 2025

    @melvin-bot

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

  8. melvin-bot commented on Sep 12, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.12-4 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-09-19. 🎊

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

  9. melvin-bot commented on Sep 12, 2025

    @melvin-bot

    BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@DylanDylann] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
    • [@sonialiap] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.
  10. melvin-bot commented on Sep 19, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Contributor: @narefyev91 is from an agency-contributor and not due payment
    • Reviewer: @DylanDylann owed $250 via NewDot

    BugZero Checklist (@sonialiap)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  11. sonialiap commented on Sep 23, 2025

    @sonialiap
  12. DylanDylann commented on Sep 25, 2025

    @DylanDylann
    Contributor

    @sonialiap We already shared a payment summary earlier: #67289 (comment)

  13. garrettmknight commented on Nov 11, 2025

    @garrettmknight
    Contributor

    $375 approved for @DylanDylann via this payment summary

  14. dukenv0307 commented on Apr 26, 2026

    @dukenv0307
    Contributor

    Coming from #88255, we shouldn't use baseFontStyle since it is designed for react-native-render-html, not regular components

  15. sobitneupane commented on May 14, 2026

    @sobitneupane
    Contributor

    Coming from #83130, merchant rules deleted before duplicating(offline) reappeared in duplicated workspace. The issue was handled in #87737 PR.

  16. ChavdaSachin commented on Jun 9, 2026

    @ChavdaSachin
    Contributor

    Coming from - #91965, a possibility of the tagGroup.tags being undefined/null were ignored here, which led to #91965

  17. sobitneupane commented on Jun 16, 2026

    @sobitneupane
    Contributor

    This issue was missed during the implementation. When duplicating a workspace, the enabled/disabled state of report fields is not preserved.

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 productionNewFeatureSomething to build that is a new item.WeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions