Skip to content

[$500] [Due for payment 2025-02-13] [Add onboarding for new workspaces being created] Create new setup tasks when users create a workspace #53509

Closed

Description

@francoisl

Part of the project "Adding onboarding for new workspaces being created"

Main issue: #48591
Doc section: https://docs.google.com/document/d/19u6ZQbNuF-v5oovIkQlmwYV4SXeAgey50pymsj5QHRY/edit?tab=t.0#heading=h.vwt3yefp8jmh (External only)

Feature Description

When a user who didn't choose the option "Manage my team's expenses" during the initial onboarding eventually creates a workspace, create onboarding tasks to teach them what to do next.

Implementation steps

  1. Prep work:

    1. Add new constant newDotTrackWorkspace to backendOnboardingChoices - Design doc section
    2. Extract the logic to generate the request and optimistic data for onboarding tasks out of completeOnboarding(), for clarity and reusability – Design doc section
  2. Create new setup tasks when users create a workspace

    • Design doc section ('External' section only)
    • Update CategorizeTrackedExpense, ShareTrackedExpense, and CreateWorkspace to generate and pass the new onboarding task data to the API if the user doesn't already have a createWorkspace onboarding task
Issue OwnerCurrent Issue Owner: @francoisl

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    on Dec 4, 2024
  2. self-assigned this
    on Dec 4, 2024
  3. francoisl commented on Dec 4, 2024

    @francoisl
    ContributorAuthor

    (Keeping internal because we're going to work with a C+ on this)

  4. mananjadhav commented on Dec 5, 2024

    @mananjadhav
    Collaborator

    Reviewed the design document. Will take another pass to see if there are any gaps. Will start with the implementation by tomorrow.

  5. mananjadhav commented on Dec 10, 2024

    @mananjadhav
    Collaborator

    @francoisl Is there anything pushed on the backend to start this?

  6. francoisl commented on Dec 10, 2024

    @francoisl
    ContributorAuthor

    One part is deployed, another one won't be until at least tomorrow, and the tasks won't be saved until both parts are.

    For now, the part 1 "Prep work" I described above shouldn't require any backend changes. Also, for step 2 we can start saving the task data in the optimistic data of the API request, and test it offline?

  7. francoisl commented on Dec 12, 2024

    @francoisl
    ContributorAuthor

    @mananjadhav the backend changes for passing guidedSetupData and engagementChoice to the API commands CategorizeTrackedExpense, ShareTrackedExpense, and CreateWorkspace are now live. Let me know if anything is not working as expected.

  8. mananjadhav commented on Dec 12, 2024

    @mananjadhav
    Collaborator

    Okay thanks. I'll check those and reach out to you if any questions.

  9. mananjadhav commented on Dec 16, 2024

    @mananjadhav
    Collaborator

    Started with this, the PR will be up by tomorrow.

  10. melvin-bot commented on Dec 19, 2024

    @melvin-bot

    @francoisl, @mananjadhav Whoops! This issue is 2 days overdue. Let's get this updated quick!

  11. 68 remaining items

  12. mallenexpensify commented on Feb 23, 2025

    @mallenexpensify
    Contributor

    We def want regression tests for new features, sometimes they're created all at once as part of a project and sometimes they're done per feature. @francoisl do you know how we want to handle here? Thx

  13. melvin-bot commented on Feb 24, 2025

    @melvin-bot

    @francoisl, @mananjadhav, @mallenexpensify, @ishpaul777 Whoops! This issue is 2 days overdue. Let's get this updated quick!

  14. mananjadhav commented on Feb 25, 2025

    @mananjadhav
    Collaborator

    Quick bump @francoisl

  15. francoisl commented on Feb 26, 2025

    @francoisl
    ContributorAuthor

    I opened an internal issue to create the regression tests
    https://github.com/Expensify/Expensify/issues/474370

  16. francoisl commented on Feb 26, 2025

    @francoisl
    ContributorAuthor

    @mallenexpensify as far as I can tell, we just need to issue the payments and close this?

  17. parasharrajat commented on Feb 27, 2025

    @parasharrajat
    Member

    Looks like PR of this isue caused an issue #57499

  18. ishpaul777 commented on Feb 27, 2025

    @ishpaul777
    Contributor

    not denying, but can you help me understand reason for your suspicion @parasharrajat also I am not able to reproduce the issue

  19. parasharrajat commented on Feb 27, 2025

    @parasharrajat
    Member

    Try to fail the workspace creation with an error, and it will create that issue. I checked the onyx keys that affect that UI state and all of them were present in the failure state.

    It might be backend but if you can give it a try and confirm this, it would be great.

  20. mallenexpensify commented on Feb 28, 2025

    @mallenexpensify
    Contributor

    Going to wait a min for payment, pending potential regression. Note to self to check the regression timeline/window too.

  21. ishpaul777 commented on Mar 1, 2025

    @ishpaul777
    Contributor

    I tried to simulate as shown in video of issue but I could not get such error when using Troubleshoot -> Simulate failing network requests

  22. mananjadhav commented on Mar 3, 2025

    @mananjadhav
    Collaborator

    I cannot reproduce it either.

    Going to wait a min for payment, pending potential regression. Note to self to check the regression timeline/window too.

    @mallenexpensify This issue was supposed to be closed by Feb 13 and I think it's already paid out. I think we should close this issue and discuss in the linked issue.

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 productionDailyKSv2InternalRequires API changes or must be handled by Expensify staff

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions