-
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 2023-09-27] [$1000] Add PrivateNotes pages to allow users to add private notes on report #25489
Comments
Although this is a new feature, we need the help of a C+ member to review it. I am adding the bug label so a bug-zero member can assist with the payment. Thanks |
Triggered auto assignment to @strepanier03 ( |
This comment was marked as off-topic.
This comment was marked as off-topic.
Job added to Upwork: https://www.upwork.com/jobs/~018981f5d13dbcc635 |
Current assignee @strepanier03 is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane ( |
Current assignee @sobitneupane is eligible for the Internal assigner, not assigning anyone new. |
@sobitneupane, I have a draft PR ready here #25490. Once it's ready for review, I'll ping you. In the meantime, please review the GH description to familiarize yourself with this new feature. Let me know if you have any questions. Thanks. |
I'll follow along until my action or payment is needed. Feel free to ping me if I miss something I need to do. |
Made some progress today, hoping to get it ready by tomorrow. |
Thanks @techievivek! |
@strepanier03, @sobitneupane, @techievivek Whoops! This issue is 2 days overdue. Let's get this updated quick! |
We got this merged today, huge thanks to @sobitneupane for prioritizing this. 🙇 |
Woohoo, thank you @sobitneupane and @techievivek! |
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 1.3.71-12 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 2023-09-27. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
This is a new feature. So, bugZero checklist is not applicable here. |
Regression Test Proposal
|
@sobitneupane Can we create a separate test for the team's expensify to ensure it receives focused attention as they are superusers for this feature? |
I am suggesting a test for it. |
Hmm, they don't have access to any expensify email address or team expensify email address so I think we can just put it in the regression test proposal but they will never be able to test that. |
Ok, just created the issue for adding the new regression tests. |
Back in office just in time for this to be paid, working on it now. |
Thank you @techievivek for helping out with the regression test step 🙌 |
Payment summary
@sobitneupane - Please put in your manual request for payment and I'll assign Jason once you confirm that's done. |
@sobitneupane Did you have a look at the above comment and put a manual request? |
Sorry for the delay. I will make the request by the weekend. In the meantime, I think we are good to close this issue. |
Ok, great, thanks. |
Requested payment on newDot |
$1,000 payment approved for @sobitneupane based on BZ summary. |
High-level of proposed solution
Add a private notes section to the ‘details’ pane of each room and DM to allow all new dot users to collect notes about other users/rooms while messaging customers. Each room and DM will have one, continuous private note. This will save the step of switching apps when taking/referring to notes and encourage users to use NewDot when messaging by making it our source of truth for contact information.
Add a section in details for private notes
We’ll add a section in the details pane with the title ‘Private Notes’. In the Personal Details of a DM, it will fit below the ‘Message ’ section. In the Room Details, it will fit between the ‘Invite’ and ‘Leave Room’ sections. We’ll keep the character limit of 15k we’re currently using for messages to standardize.
Create a single note for each DM and room for each member
Each room and DM will have a single, continuous note for each member. To maintain consistency with other forms and textboxes, we’ll include a ‘Save’ button and allow users to write in markdown.
Ex. In a DM between Ava and Betty, there will be two notes. In a room where Ava, Betty, and Callum are all members, there will be three notes. None of the members will be able to access another member’s note (except in the special situation immediately below).
Allow Team Expensify user and Expensify employees to view notes added by other Team Expensify users
Context in Guides’ private notes will be helpful when a customer gets a new “owner” (e.g. AM steps in after a won deal, Guide steps in after another Guide leaves). Additionally, these notes will be helpful to a Guide’s mentor when catching up on what’s happening in preparation for a call and keeping track of a deal in general.
To give the new owner and/or mentor visibility into the notes for a deal/customer, we’ll allow users with @expensify.com (Mentors) and @team.expensify.com (Guides and AMs) logins to view notes written by @team.expensify.com logins in rooms and DMs they are members of.
Notes for Completeness:
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: