-
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
[Hold for payment] [$1000] Welcome Message Visibility Bug: User A Can See Welcome Message Intended for User B #20990
Comments
Triggered auto assignment to @NicMendonca ( |
Bug0 Triage Checklist (Main S/O)
|
ProposalPlease re-state the problem that we are trying to solve in this issue.Welcome Message Visibility Bug: User A Can See Welcome Message Intended for User B What is the root cause of that problem?In What changes do you think we should make in order to solve the problem?We could add a check App/src/pages/home/report/ReportActionItem.js Line 425 in 23ca9a7
or add this check above here to only hide the content of message App/src/pages/home/report/ReportActionItem.js Line 483 in 23ca9a7
What alternative solutions did you explore? (Optional) |
Job added to Upwork: https://www.upwork.com/jobs/~01d954ce545b1fc7fc |
Current assignee @NicMendonca is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @aimane-chnaif ( |
@aimane-chnaif bump on the above proposal ^^ |
ProposalPlease re-state the problem that we are trying to solve in this issue.In my opinion, this is expected behavior if the user is a workspace owner, so the owner can re-visit the welcome message chat thread from room chat. I didn't see the chat message from a third account that is not a workspace owner. The actual issue here is the text Please correct me if I'm mistaken. What is the root cause of that problem?I've noticed that What changes do you think we should make in order to solve the problem?We can change it to App/src/pages/home/report/ReportActionItem.js Line 444 in 342d4fd
like what we did here. To make it make more sense, then we can add the workspace owner to the What alternative solutions did you explore? (Optional)N/A |
Triggered auto assignment to @conorpendergrast ( |
This comment was marked as duplicate.
This comment was marked as duplicate.
@conorpendergrast I am going OOO until Wednesday. Can you watch this while I am away? I'll unassign you when I am back. Thank you! |
Of course! Toodles |
Thanks for the discussion here! Given that this will be addressed in the #21822 we should close this out. Are there any other actions we need to take here? |
@robertjchen I reviewed that PR. I think it's better to handle compensation here. And also @avi-shek-jha might be eligible for bug reporting bonus. |
@robertjchen You need to leave it open until we merge the PR to pay the reporting bonus or any review bonus |
Got it, thanks for the clarification! Since @pecanoro handled all the questions here, I'll re-assign for credit! 🙇 |
Current assignee @aimane-chnaif is eligible for the Internal assigner, not assigning anyone new. |
@puneetlath, @pecanoro, @NicMendonca, @aimane-chnaif Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
I believe this was fixed via #21822 which was deployed to production 5 days ago. So @NicMendonca I think you just need to pay out the issue reporter and then this is good to go. |
FYI @puneetlath |
@tranvantoan-qn from your screenshot, I am not sure what bug it is. Can you please elaborate more with repro step? |
@aimane-chnaif As the bug's title mentioned In this case, I'm user A, and user B is the one I'm highlighted Since it's the whisperer message sent by the system, it should say:
I didn't test this case intentionally, but It happened to me when I join this room |
@tranvantoan-qn user A is admin right? It's not bug but expected. Please read through full discussion in this GH. |
@aimane-chnaif |
@tranvantoan-qn You need to provide some reproduction steps |
@NicMendonca Friendly reminder to pay the reporting bonus to @avi-shek-jha so we can close this 🙏 |
Also #20990 (comment) |
Ahh you are right, @NicMendonca We also need to pay @aimane-chnaif for internal review!! |
@avi-shek-jha @aimane-chnaif can you please apply to the job? https://www.upwork.com/jobs/~01d954ce545b1fc7fc |
Thanks. Applied. |
@aimane-chnaif sent you the offer |
@aimane-chnaif paid! @@avi-shek-jha just need you to accept the offer, thanks! |
everyone has been paid! 🎉 thank all! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
Message intended for User B should NOT be visible to User A (or “message ONLY visible to User B should be removed”)
Actual Result:
Welcome message was visible to User A with a notation ‘only visible to User B’
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.29-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
welcome.message.vulnerability.mp4
Recording.1014.mp4
Expensify/Expensify Issue URL:
Issue reported by: @avi-shek-jha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1686355332887919
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: