Skip to content
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

Open
garrettmknight opened this issue Nov 1, 2024 · 30 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production External Added to denote the issue can be worked on by a contributor Internal Requires API changes or must be handled by Expensify staff NewFeature Something to build that is a new item. Weekly KSv2

Comments

@garrettmknight
Copy link
Contributor

garrettmknight commented Nov 1, 2024

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.

  • Start returning the user's WS chat as part of the OpenPolicyInitialPage API call and the OpenPolicyProfilePage API Call since on wide view only the profile one is called.
  • Add separator text below WS items in the WS details LHN that reads "Submit expenses using your workspace chat below:"
    • Spanish translation: "Envíe los gastos utilizando el chat de su espacio de trabajo:"
  • Add an LHN row that mirrors the look of the user's WS chat in the inbox.
  • Selecting the WS chat row in LHN will navigate to the WS chat report for that WS.

image

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021854205244452205878
  • Upwork Job ID: 1854205244452205878
  • Last Price Increase: 2024-11-06
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @garrettmknight
@garrettmknight garrettmknight added Daily KSv2 NewFeature Something to build that is a new item. labels Nov 1, 2024
@garrettmknight garrettmknight self-assigned this Nov 1, 2024
Copy link

melvin-bot bot commented Nov 1, 2024

Triggered auto assignment to @trjExpensify (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 melvin-bot bot added Weekly KSv2 and removed Daily KSv2 labels Nov 1, 2024
@garrettmknight garrettmknight added Daily KSv2 and removed Weekly KSv2 labels Nov 1, 2024
@melvin-bot melvin-bot bot added the Overdue label Nov 4, 2024
@flaviadefaria flaviadefaria moved this to First Cohort in [#whatsnext] #migrate Nov 4, 2024
Copy link

melvin-bot bot commented Nov 4, 2024

@garrettmknight Whoops! This issue is 2 days overdue. Let's get this updated quick!

@garrettmknight
Copy link
Contributor Author

Still discussing how best to implement.

@melvin-bot melvin-bot bot removed the Overdue label Nov 4, 2024
@garrettmknight
Copy link
Contributor Author

We've landed on the high level, now we just need to recruit someone to build it!

@garrettmknight garrettmknight added the External Added to denote the issue can be worked on by a contributor label Nov 6, 2024
@melvin-bot melvin-bot bot changed the title [NewDot Feature Request] Add route to WS chat in Workspace menu [$250] [NewDot Feature Request] Add route to WS chat in Workspace menu Nov 6, 2024
Copy link

melvin-bot bot commented Nov 6, 2024

Job added to Upwork: https://www.upwork.com/jobs/~021854205244452205878

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Nov 6, 2024
Copy link

melvin-bot bot commented Nov 6, 2024

Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt (External)

@nkdengineer
Copy link
Contributor

nkdengineer commented Nov 6, 2024

Edited by proposal-police: This proposal was edited at 2024-11-06 17:15:56 UTC.

Proposal

Please 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?

  1. We should get the policy expense report by filtering from allReports. This will be the policy expense chat that has policyID is the viewing policyID and has isOwnPolicyExpenseChat is true. We can re-use getPolicyExpenseChat function with ownerAccountID is currentUserAccountID and the policyID is the viewing policyID

  2. After getting the report, we can add the text and LHN row below the workspace feature here

  • The text is the description here

Add separator text below WS items in the WS details LHN that reads "Submit expenses using your workspace chat below:"
Spanish translation: "Envíe los gastos utilizando el chat de su espacio de trabajo:"

  • The LHN row will contain the avatar of the policy expense chat and the right icon, we can reuse MenuItem component or other component like this. To get the avatar, we can use getIcons function as we did here to get the icon of the policy expense chat. Then when we click on this row, we will navigate to the report screen with the reportID is the ID of the policy expense chat

What alternative solutions did you explore? (Optional)

@garrettmknight
Copy link
Contributor Author

@shahinyan11 feel free to put a proposal together if you want. If @nkdengineer's isn't complete and yours is we'll assign you.

@shahinyan11
Copy link

@garrettmknight Thanks. But @nkdengineer's proposal is good enough. I most likely won't propose.

@s77rt
Copy link
Contributor

s77rt commented Nov 6, 2024

@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
Link to proposal

Copy link

melvin-bot bot commented Nov 6, 2024

Triggered auto assignment to @youssef-lr, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

Copy link

melvin-bot bot commented Nov 22, 2024

Current assignee @s77rt is eligible for the External assigner, not assigning anyone new.

@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Nov 22, 2024
@grgia grgia removed Help Wanted Apply this label when an issue is open to proposals by contributors Hot Pick Ready for an engineer to pick up and run with labels Nov 22, 2024
@garrettmknight garrettmknight added Weekly KSv2 and removed Daily KSv2 labels Nov 27, 2024
@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Nov 30, 2024
@melvin-bot melvin-bot bot changed the title [$250] [NewDot Feature Request] Add route to WS chat in Workspace menu [HOLD for payment 2024-12-07] [$250] [NewDot Feature Request] Add route to WS chat in Workspace menu Nov 30, 2024
Copy link

melvin-bot bot commented Nov 30, 2024

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

@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Nov 30, 2024
Copy link

melvin-bot bot commented Nov 30, 2024

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:

  • @s77rt requires payment through NewDot Manual Requests
  • @nkdengineer requires payment (Needs manual offer from BZ)

Copy link

melvin-bot bot commented Nov 30, 2024

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:

  • [@s77rt] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
  • [@garrettmknight] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

@s77rt
Copy link
Contributor

s77rt commented Dec 1, 2024

Not a bug ^ No regression test needed

@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Dec 7, 2024
Copy link

melvin-bot bot commented Dec 7, 2024

Payment Summary

Upwork Job

  • Reviewer: @s77rt owed $250 via NewDot
  • ROLE: @nkdengineer paid $(AMOUNT) via Upwork (LINK)

BugZero Checklist (@garrettmknight)

  • I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
  • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1854205244452205878/hired)
  • I have paid out the Upwork contracts or cancelled the ones that are incorrect
  • I have verified the payment summary above is correct

@garrettmknight
Copy link
Contributor Author

garrettmknight commented Dec 9, 2024

Payment summary:

  • Reviewer: @s77rt owed $250 via NewDot - Note that this should have been $125 since there was a regression. I'll reopen this and close when I've confirmed the difference has been applied to another payment.
  • Contributor: @nkdengineer $125 - awaiting Upwork profile

@JmillsExpensify
Copy link

$250 approved for @s77rt

@garrettmknight garrettmknight added Weekly KSv2 and removed Daily KSv2 labels Dec 9, 2024
@garrettmknight
Copy link
Contributor Author

Dropping to weekly while we work out @nkdengineer's upwork profile.

@nkdengineer
Copy link
Contributor

@garrettmknight My Upwork profile here: https://www.upwork.com/freelancers/~0134d0b74faef1a5ac. I've added this to the GitHub's profile.

@s77rt
Copy link
Contributor

s77rt commented Dec 13, 2024

I just remembered this caused a regression and it should be $125.

@garrettmknight
Copy link
Contributor Author

Thanks for the heads up @s77rt - can you reflect the change on another payment since it's difficult to claw back $$$ via NewDot?

@garrettmknight
Copy link
Contributor Author

@s77rt
Copy link
Contributor

s77rt commented Dec 13, 2024

Thanks @garrettmknight I have asked for next steps (if possible) here. Otherwise I will deduct this from another payment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production External Added to denote the issue can be worked on by a contributor Internal Requires API changes or must be handled by Expensify staff NewFeature Something to build that is a new item. Weekly KSv2
Projects
Status: First Cohort - MEDIUM or LOW
Development

No branches or pull requests

8 participants