Skip to content

Create components for Workspace Downgrade #51494

Closed

Description

@carlosmiceli

Part of Add Workspace Plan Downgrades to NewDot

Doc section

Steps to complete:

  • Update Workspace Profile Page
  • Create Plan Type RHP
  • Create Downgrade Confirmation RHP
  • Create Downgrade Success RHP
  • Create Downgrade Success RHP for admins of other Control workspaces
Issue OwnerCurrent Issue Owner: @DylanDylann

Activity

  1. melvin-bot commented on Oct 25, 2024

    @melvin-bot

    Triggered auto assignment to @twisterdotcom (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 Oct 25, 2024

    @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 Oct 25, 2024

    @melvin-bot

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

  4. DylanDylann commented on Oct 29, 2024

    @DylanDylann
    Contributor

    @carlosmiceli Could we divide this issue into multiple PRs?

    cc @jasperhuangg

  5. DylanDylann commented on Oct 29, 2024

    @DylanDylann
    Contributor

    @carlosmiceli

    I notice that we need to create these tasks:

    • Create Plan Type Page
    • Create a generic success component
    • Upgrade #admins messaging and workspace owner whisper
  6. carlosmiceli commented on Oct 29, 2024

    @carlosmiceli
    ContributorAuthor

    Sorry about the delay, have been sick the last couple of days 🙏

    I don't see why not have multiple PRs if you think that's best.

  7. carlosmiceli commented on Oct 29, 2024

    @carlosmiceli
    ContributorAuthor

    @DylanDylann isn't the success component the same as the confirmation component?

    When you say plan type page, do you mean the workspace downgrade page? Btw, I think @jayeshmangwani already put that page together on the other PR, but since it's a PR about routes I think it shouldn't be included there. Can we move that into a the new PR that Dylan is going to work on so it's better organized according to the issues' scopes?

    I'll create an issue about upgrades soon, but let me get back to you on that later this week 👍

  8. 33 remaining items

  9. DylanDylann commented on Nov 29, 2024

    @DylanDylann
    Contributor

    @carlosmiceli Any update on the BE changes

  10. carlosmiceli commented on Nov 29, 2024

    @carlosmiceli
    ContributorAuthor

    It's under review, hopefully merged soon! 🙏

  11. carlosmiceli commented on Nov 30, 2024

    @carlosmiceli
    ContributorAuthor

    Final BE PR has been merged :)

  12. garrettmknight commented on Jan 6, 2025

    @garrettmknight
    Contributor

    @DylanDylann now that the BE is on prod, do you need anything else here to finish off?

  13. DylanDylann commented on Jan 7, 2025

    @DylanDylann
    Contributor
  14. garrettmknight commented on Jan 7, 2025

    @garrettmknight
    Contributor

    Sweet - I'm going to close this one then. Once @carlosmiceli gets back we'll work through all the PRs and pay out in bulk for the project.

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

Metadata

Metadata

Labels

NewFeatureSomething to build that is a new item.ReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions