-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Workspace Chats for All] Make it possible to submit expenses to any workspace, whether or not there is a workspace chat #49344
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 un-assigning you since there's no new UI being added here. |
not overdue |
|
Moving this over to #migrate project as it will be a blocker for enabling workspace chat for existing workspaces of Cohort 1. |
Can we move this issue to |
we are making daily progress on this, Draft Pr (almost ready) here: #49412 @puneetlath is working on BE changes |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.52-5 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-10-30. 🎊 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:
|
Back-end PR for requestDistance is here: https://github.com/Expensify/Web-Expensify/pull/44129 Once that is on staging, we should be able to proceed with the reverted front-end PR. |
Likely going to change this behavior based on this discussion: https://expensify.slack.com/archives/C07NMDKEFMH/p1730152377459179?thread_ts=1730145327.196299&cid=C07NMDKEFMH I'll update here shortly. |
Ok, I've already talked to @ishpaul777 but after a lot of discussion in #migrate we have decided we are going to pause this work and instead go in a different direction. We're going to do #51804 instead for now. |
Is this on HOLD or should be closed now that we go in a different direction ?? |
@puneetlath, @allroundexperts, @ishpaul777 Eep! 4 days overdue now. Issues have feelings too... |
We should close it. Just need to pay out for the work done. |
@puneetlath lets wrap this up ? : ) to summarize: There was 3 PRs:
|
@puneetlath, @allroundexperts, @ishpaul777 Huh... This is 4 days overdue. Who can take care of this? |
Payment summary:
@ishpaul777 offer is here: https://www.upwork.com/nx/wm/offer/104882055. Please ping me on this issue when you've accepted. @allroundexperts please request in NewDot. |
Accepted the offer! Thanks! |
Paid. Thanks y'all! |
Problem
There are a few different ways users can end up in a scenario in NewDot where they aren't able to submit expenses to their workspace. A couple known scenarios:
Solution
Update NewDot to allow submitting to any policy you are a member of, whether or not a workspace chat exists for it. The back-end will then handle creating a workspace chat for the expense if necessary. This would solve the problem for both 1 and 2.
To do this we will:
isPolicyExpenseChatEnabled=true
in the submit expense dialog, whether or not workspace chats exist for themIssue Owner
Current Issue Owner: @puneetlathThe text was updated successfully, but these errors were encountered: