Closed lanitochka17 closed 3 months ago
Triggered auto assignment to @anmurali (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
@anmurali FYI 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 that this bug might be related to #vip-vsp
@anmurali Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
@anmurali Still overdue 6 days?! Let's take care of this!
Job added to Upwork: https://www.upwork.com/jobs/~01c628cdc0c39c744f
Triggered auto assignment to Contributor-plus team member for initial proposal review - @allgandalf (External
)
This seems like an edge case so I am going to make it a medium priority bug but if we get someone to fix it, great!
Maybe the Whisper component should update the room creation message whenever the message is edited.
๐ฃ @devguest07! ๐ฃ Hey, it seems we donโt have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork. Please follow these steps:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
Contributor details Your Expensify account email: devguest07@gmail.com Upwork Profile Link: https://www.upwork.com/freelancers/~01020d097e810d1b07
โ Contributor details stored successfully. Thank you for contributing to Expensify!
Waiting for proposals โฆ..
@anmurali @allgandalf this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
Waiting for proposals.....
๐ฃ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? ๐ธ
@anmurali, @allgandalf Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
Bumped on slack for proposals
I believe Whisper in this case is created by the backend, and there is nothing we can do from the front-end to fix this. There are no actions (APIs) in frontend that we can use to re-create the whisper.
@anmurali, @allgandalf Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
Still waiting for proposals ....
๐ฃ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? ๐ธ
I think the issue is from the backend.
When we mention a non-created room, the Concierge Expensify will ask the user to create the room because it doesn't exist. So when we edit the comment and change the room name, and click yes (before asking us to create a room) to concierge Expensify, the bot doesn't change the room name from the updated comment. For example: The bot asking to create room1 but when we changed the room name to room12, the bot didn't update the room name. So, when we click yes, the bot will wrap the room1 text only and not wrap the 2
last character inside the mention-room tag
But for the functionality wrapping text in the mention room tag is on the backend not on the frontend
@anmurali @allgandalf this issue is now 4 weeks old, please consider:
Thanks!
@anmurali, @allgandalf Eep! 4 days overdue now. Issues have feelings too...
@anmurali , do you think we should increase the bounty to get some ๐
๐ฃ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? ๐ธ
@anmurali, @allgandalf Whoops! This issue is 2 days overdue. Let's get this updated quick!
@anmurali , what do you think about this?
๐ฃ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? ๐ธ
bump @anmurali
@anmurali, @allgandalf Huh... This is 4 days overdue. Who can take care of this?
Raised it to $500.
Upwork job price has been updated to $500
The first half of the room mention is highlighted when the room mention is different
We called an API to update a comment. I saw that the text was updated, but the last message HTML mention-report
did not update yet. We then called ResolveActionableReportMentionWhisper
to resolve the action report mention whisper with the report action ID, but it used the old, not updated text, causing the issue.
Check the UpdateComment API to see why the text did not update. I believe if the UpdateComment
API updates the text correctly, this issue will be resolved
Posted on slack for more ๐
๐ฃ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? ๐ธ
@anmurali, @allgandalf Huh... This is 4 days overdue. Who can take care of this?
Still waiting for proposals...
I posted again on the open source channel to ask for proposals, do let me know of the next steps if we do not get new proposals by the next overdue label
BE issue
I feel this issue is backend.
I'm not sure how backend is resolving the whisper message, we're receiving a new reportAction i.e whisper message with a param reportNames
with the mention we've done. After we update the comment we're not receiving or updating the whisper message when we click yes
for whisper message we're just sending the reportActionID
for the whisper message.
I think we should update the whisper reportAction with the newly updated comment.
Maybe a new API call calling from frontend or backend directly can update the whisper report-action using the updateComment
method itself.
๐ฃ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? ๐ธ
@anmurali, @allgandalf Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
still waiting for proposals......
@allgandalf hope you read the comments above, we think it's backend issue. Are you confident this can be solved from frontend that's why you're waiting for proposals or is there any other reason?!
@anmurali, @allgandalf Whoops! This issue is 2 days overdue. Let's get this updated quick!
@allgandalf hope you read the comments above, we think it's backend issue. Are you confident this can be solved from frontend that's why you're waiting for proposals or is there any other reason?!
I wanted a FE/upstream fix for this, I want to match the Expected results:
The new room mention in edit message in Step 4 will not be highlighted because the mentioned room is different from the room created from the whisper
But now i'm unsure if this should be fixed on the FE
/BE
, @anmurali should we put up an internal label here?
๐ฃ It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? ๐ธ
@anmurali, @allgandalf Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
If you havenโt already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.4.76 Reproducible in staging?: Y Reproducible in production?: Y If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Issue reported by: Applause - Internal Team
Issue found when executing PR https://github.com/Expensify/App/issues/40857
Action Performed:
Expected Result:
The new room mention in edit message in Step 4 will not be highlighted because the mentioned room is different from the room created from the whisper
Actual Result:
The first half of the room mention is highlighted when the room mention is different
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/78819774/72c34807-6fe8-4325-8382-78249d5c5b3d
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @allgandalf