-
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-12-07] [$250] [NewDot Feature Request] Add route to WS chat in Workspace menu #51851
Comments
Triggered auto assignment to @trjExpensify ( |
@garrettmknight Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Still discussing how best to implement. |
We've landed on the high level, now we just need to recruit someone to build it! |
Job added to Upwork: https://www.upwork.com/jobs/~021854205244452205878 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt ( |
Edited by proposal-police: This proposal was edited at 2024-11-06 17:15:56 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.Add route to WS chat in Workspace menu What is the root cause of that problem?This is a new feature request What changes do you think we should make in order to solve the problem?
What alternative solutions did you explore? (Optional) |
@shahinyan11 feel free to put a proposal together if you want. If @nkdengineer's isn't complete and yours is we'll assign you. |
@garrettmknight Thanks. But @nkdengineer's proposal is good enough. I most likely won't propose. |
@nkdengineer Thanks for the proposal. Overall looks good to me. (ownerAccountID does not have to be currentUserAccountID as employees should see the policy too). 🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @youssef-lr, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Current assignee @s77rt is eligible for the External assigner, not assigning anyone new. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.68-7 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-12-07. 🎊 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:
|
Not a bug ^ No regression test needed |
Payment Summary
BugZero Checklist (@garrettmknight)
|
Payment summary:
|
$250 approved for @s77rt |
Dropping to weekly while we work out @nkdengineer's upwork profile. |
@garrettmknight My Upwork profile here: https://www.upwork.com/freelancers/~0134d0b74faef1a5ac. I've added this to the GitHub's profile. |
I just remembered this caused a regression and it should be $125. |
Thanks for the heads up @s77rt - can you reflect the change on another payment since it's difficult to claw back $$$ via NewDot? |
Thanks @garrettmknight I have asked for next steps (if possible) here. Otherwise I will deduct this from another payment |
Slack conversation (hyperlinked to channel name): https://expensify.slack.com/archives/C07NMDKEFMH/p1730380892061729
Problem: Many users (like this one) are visibly confused about how to submit expenses for reimbursement to a workspace and find themselves in the Workspace menu during their search.
Solution: Let's add a route in the Workspace details page that navigates to the user's workspace chat for that workspace.
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @garrettmknightThe text was updated successfully, but these errors were encountered: