-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2024-11-21] Re-direct to Classic when creating expenses for non-migrated users #51804
Comments
Current assignee @puneetlath is eligible for the NewFeature assigner, not assigning anyone new. |
|
Triggered auto assignment to Design team member for new feature review - @dubielzyk-expensify ( |
@dubielzyk-expensify can you help with some mocks of what that re-direct to Classic modal should look like? |
Yes sir. Think we need some @jamesdeanexpensify magic to make the copy more crisp (he's back on Monday I believe). Mockscc @Expensify/design for vizzzibilities |
ProposalPlease re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?
The similar should be applied with Track expense and Send invoice options. What alternative solutions did you explore? (Optional) |
👋 I'll take this |
Based on the latest discussions, I think this bow belongs to #retain, so I am assigning it there. |
@puneetlath @dubielzyk-expensify too much?
|
It's quite cute. But this feature is still available right, but it's just because the workspace has a complicated setup that we don't allow it? So maybe it feels a bit underselling? |
Updated it slightly. Anything else specific you wanna tweak? Happy to brainstorm. |
I like it. Keen to hear what @puneetlath thinks though |
Sounds great to me! FYI @ishpaul777 |
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. |
Looks like we have another flow in-product where we need to redirect to Classic: #52457 Would @ishpaul777 want to take that over as well? Or shall we treat it as a separate follow up? |
Happy to take it :) can raise a Pr in 6-8 hours |
1 similar comment
Happy to take it :) can raise a Pr in 6-8 hours |
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. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.61-3 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 2024-11-21. 🎊 For reference, here are some details about the assignees on this issue:
|
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:
|
Payment Summary
BugZero Checklist (@puneetlath)
|
@suneox can you complete the checklist here? |
BugZero Checklist
Regression Test ProposalStep 1: Create a control workspace on a new account in OldDot. Do we agree 👍 or 👎 |
@puneetlath, @suneox, @ishpaul777, @dubielzyk-expensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@ishpaul777 offer here: https://www.upwork.com/nx/wm/offer/105064871 Can y'all ping me here when you've accepted? Regression test GH: https://github.com/Expensify/Expensify/issues/447666 |
Thank you! I have accepted the offer @puneetlath |
@ishpaul777 has been paid. |
I've accepted the offer. Thank you |
Everyone has been paid now. Thanks everyone! |
There are scenarios where users who have not yet had their group workspaces NewDot-enabled in NewDot. In those scenarios, things can get confusing if they try to create expenses.
To address this, let's block them from Creating, Tracking, Submitting expenses from NewDot if they are:
We should do this by showing a modal when they tap/click any of these options, which re-directs them back to OldDot.
Issue Owner
Current Issue Owner: @puneetlathThe text was updated successfully, but these errors were encountered: