[HOLD for payment 2025-01-02] Hook up with the Downgrade Workspace API

[carlosmiceli]

Part of Add Workspace Plan Downgrades to NewDot

Doc section

Steps to complete:

• Create a new action
• Connect it with the downgrade button

Issue Owner

Current Issue Owner: @sonialiap

[melvin-bot]

Triggered auto assignment to @sonialiap (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.

[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 ⚠️

[melvin-bot]

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

[carlosmiceli]

This will be the final issue to complete, so it needs to HOLD on all the other issues from the project. Will assign contributor then.

[shawnborton]

I think we're still holding on this one, right?

[carlosmiceli]

Will try to make progress today.

[carlosmiceli]

We are close to being able to do this, final BE PR is in review and we can start testing FE and BE together.

[carlosmiceli]

Hey @DylanDylann, this should be ready to tackle now that the BE is complete :)

[sonialiap]

@DylanDylann this feature is ready for the FE part! Will you be able to handle this one?

[DylanDylann]

@carlosmiceli Yeah I already did the FE implementation locally with a branch built up from #53343. I will raise PR after #53343 is merged

[carlosmiceli]

Great!

[sonialiap]

I'm OOO Dec 16-20, I don't think this will need a BZ before I'm back, but if it does please reapply the bug label

[melvin-bot]

@carlosmiceli, @shawnborton, @sonialiap, @DylanDylann Whoops! This issue is 2 days overdue. Let's get this updated quick!

[carlosmiceli]

Not overdue, we're working on it :D

[carlosmiceli]

@DylanDylann I think I found the issue with the duplicate action, but can we proceed using the first one while I try to fix it?

[carlosmiceli]

Fixed, will be merged soon. The action that says this workspace instead of the policy name is the right one.

[DylanDylann]

Please ping me when the change is deployed

[carlosmiceli]

It's now deployed.

[DylanDylann]

@carlosmiceli Worked well

[carlosmiceli]

Fantastic, thanks sir! cc @garrettmknight

I'll go over all the open issues tomorrow to see what's left to do, but anything outstanding from your end @DylanDylann ?

[DylanDylann]

Everything works well from me

[carlosmiceli]

To confirm, this is still the plan, correct?

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

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]

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

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.78-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Downgrade Feature #54356

If no regressions arise, payment will be issued on 2025-01-02. 🎊

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

• @DylanDylann requires payment (Needs manual offer from BZ)

[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.