-
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-07-24] [$1000] Web - Thread report and LHN title still visible after thread parent message being flagged as Intimidation or Bullying #21890
Comments
Triggered auto assignment to @joekaufmanexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
ProposalAmjedNazzal on GH Please re-state the problem that we are trying to solve in this issue.Thread report and LHN title still visible after thread parent message being flagged as Intimidation or Bullying What is the root cause of that problem?The text used for the titles of OptionRowLHN is retrieved from ReportUtils.getReportName which isn't handling the case where the parent message has been reported as Intimidation/Bullying or has been hidden. Lines 372 to 374 in 6183609
What changes do you think we should make in order to solve the problem?We could firstly add a new entry to parentReportAction and for example call it hiddenMessage and give it a value similar to deletedMessage. if (
lodashGet(parentReportAction, 'message[0].moderationDecisions[0].decision') === CONST.MODERATION.MODERATOR_DECISION_PENDING_HIDE ||
lodashGet(parentReportAction, 'message[0].moderationDecisions[0].decision') === CONST.MODERATION.MODERATOR_DECISION_HIDDEN
) {
return Localize.translateLocal('parentReportAction.hiddenMessage');
} ResultScreen.Recording.2023-06-28.at.5.09.28.PM.mov |
I can reproduce. We decided to split this off from #21497 (comment) . Seems like expected behavior here is:
|
Job added to Upwork: https://www.upwork.com/jobs/~013a0825ff8c5c6ab6 |
Current assignee @joekaufmanexpensify is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @thesahindia ( |
Not overdue. Waiting for proposals |
@joekaufmanexpensify There is my proposal by the way posted by kbecciv :) |
Ah, thanks! @thesahindia mind reviewing the proposal when you have a chance? |
I not sure but it's possible that it is being handled somewhere else. @dangrous was going to handle this case in a follow-up PR as mentioned in #19476 (comment). @dangrous, please let us know if this is being handled somewhere else. |
Whoops, nope, never did that. Would be great to handle it here! |
Works for me! |
@joekaufmanexpensify is it going to be like an internal fix? or is my proposal going to be reviewed? |
I'm thinking we'll review your proposal, right @thesahindia ? |
@AmjedNazzal's proposal looks good but I think we should get @shawnborton's input about the expected behaviour. What do you think about the final result @shawnborton? Screen.Recording.2023-06-28.at.5.09.28.PM.mov |
I'm not too sure here, @dangrous since you worked on moderation, what do you think? |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Behavior is certainly fine by me! Only question would be the specific copy we use. Not to suggest a ping of yet another person, but have we had marketing take a look at it? |
Sounds good! Adding marketing label to get copy input. Here's a summary of the issue, if you're assigned: If a message is reported as being intimidation for bullying, we currently hide the message in the chat, and give the option to reveal its contents. However, if the reported message has a thread report beneath it, we still show the reported message's contents in the thread report title in LHN, and then in the thread header if you click into the thread report. In this issue, we're proposing that when a message reported for bullying/intimidation has a thread beneath it, that we'll hide the reported message in LHN, and then the thread report's header. We're proposing that we do this with the following copy We're thinking this makes sense, as it follows a similar pattern to how we handle a thread's parent message being deleted ( |
@joekaufmanexpensify Friendly nudge regarding payment :) |
Thanks! Yep we just need to complete the BZ checklist before we can send payment. @thesahindia mind completing your portion? |
Okay, this one qualifies for a speed bonus, so we need to make the following payments:
|
@AmjedNazzal you're already hired, so we'll issue payment as soon as the BZ checklist is complete. |
@thesahindia once the BZ checklist is complete, please submit a payment request, and comment on the issue once you've done that! |
Bumped in Slack. |
We can skip the checklist because it wasn't a regression. We knew about this case when the main PR was open but we decided to handle it in a follow up PR. If we wanna add a test case here are steps-
|
BZ checklist is complete. |
@AmjedNazzal $1,750 sent and contract ended! |
Upwork job closed. |
@thesahindia could you please request $1,500 and comment here once complete? |
Note: payment summary message is here. |
I will request the payment in the morning. I had some bank issues so I was busy resolving them. |
All good. Thanks! |
@thesahindia did you have a chance to request payment here yet? |
I can reproduce the issue still Screen.Recording.2023-07-28.at.4.42.23.PM.mov |
I couldn't. I am facing issues while adding my bank account. I have asked about it here. You can just close the issue, I will add it to my list and will request payment once the problem gets resolved (Did the same on other tickets) |
I think it is a regression and not related to the current issue. |
i will take a look into this today. |
@sonialiap are you still able to reproduce this now? I just tested on my end, and it seemed to work. Though, I had to click into the thread after reporting the message before the title updated to |
Still figuring this out |
Okay, I tested this again, and it's working for me. So going to close this out. @sonialiap LMK if you see this not working again, and happy to look into it more. |
Please note that @thesahindia still needs to request payment, but advised we can close this in the interim, and he'll request payment once the issue with his bank account is resolved. Here's the summary of payments for when we pay this in NewDot:
|
Reviewed the details for @thesahindia. $1,500 approved for payment in NewDot based on the BZ summary above. |
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:
LHN title and thread report title should display "Message Hidden" while the parent message of the thread has MODERATOR_DECISION of PENDING_HIDE or HIDDEN
Actual Result:
LHN title and thread report title are still visible
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.33-4
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
Screen.Recording.2023-06-28.at.5.14.55.PM.1.mov
Recording.959.mp4
Expensify/Expensify Issue URL:
Issue reported by: Amjed Nazzal
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1687962396495309
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: