-
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-07-24] [$250] Room - Room mention is not copied to clipboard and editor is empty when editing room mention #40403
Comments
Triggered auto assignment to @JmillsExpensify ( |
Triggered auto assignment to @lakchote ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
@JmillsExpensify I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors. |
We think this issue might be related to the #collect project. |
Job added to Upwork: https://www.upwork.com/jobs/~01c98cde11a4c25f4e |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel ( |
Not a blocker - it's an edge case that only concer room mentions, no core customer functionality is broken. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Room - Room mention is not copied to clipboard and editor is empty when editing room mention What is the root cause of that problem?we don't handle App/src/pages/home/report/ContextMenu/ContextMenuActions.tsx Lines 395 to 398 in 9b839f4
before sending mention report text to backend we format it to be like this What changes do you think we should make in order to solve the problem?we need to handle to copy the orignal message we need to catch reportID from for that we need to add this extra .replace(/<mention-report reportID="(\d*)"\/>/gi, (match, reportID): string => {
const report = getReport(reportID);
return `<mention-report>${report?.reportName ?? report?.displayName}<mention-report/>`;
}) and App/src/pages/home/report/ContextMenu/ContextMenuActions.tsx Lines 43 to 51 in 9b839f4
What alternative solutions did you explore? (Optional) |
@JmillsExpensify I'll be OOO next week until April 29th. Feel free to assign another internal engineer to review if needed. |
Roomname is copied successfully, but the editor is still empty while editing the room mention Screen.Recording.2024-04-22.at.1.42.30.AM.mov |
Interesting, let's keep this open then |
Looks like the related issue is now merged, so removing the hold. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
1 similar comment
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@lakchote Yes, I pinged @ahmedGaber93 here #40477 (comment). I think it still makes sense to solve it together with #40477 |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
We're fixing this together with #40477 - waiting for the PR from @ahmedGaber93 |
Looks like we're waiting on the related App PR, though I'll go ahead and keep this issue as is because it shouldn't be too much longer. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.7-8 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-07-24. 🎊 For reference, here are some details about the assignees on this 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:
|
Closing, we'll handle payment and regression tests in the other issue |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.63-0
Reproducible in staging?: Y
Reproducible in production?: N
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Precondition:
Expected Result:
In Step 5, the room in the message will be copied.
In Step 7. the room in the editor will be preserved.
Actual Result:
In Step 5, the room in the message is not copied.
In Step 7. the room in the editor is missing.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6453285_1713425267404.room_mention.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @JmillsExpensifyThe text was updated successfully, but these errors were encountered: