You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[$250] Chat - You is displayed on chat header, and LHN when opening resolved duplicate messsage #75233
Version Number: 9.2.59-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:**N/A Email or phone of affected tester (no customers):expensify416+da2@gmail.com Issue reported by: Applause - Internal Team
Action Performed:
\1. Go to workspace chat
2. Create two duplicate manual expense
3. Open the expense thread > Review duplicate.> Keep all
4. Open one of the expenses > Right click on 'resolved the duplicate' message > Reply in thread
Expected Result:
'resolved the duplicate' should be displayed on LHN title, and report header
Actual Result:
'You' is displayed on LHN title, and report header
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug7004274_1763152533188.Screen_Recording_2025-11-14_at_11.27.40_at_night.mp4
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
changed the title [-]Chat - You is displayed on chat header, and LHN when opening resolved duplicate messsage[/-][+][$250] Chat - You is displayed on chat header, and LHN when opening resolved duplicate messsage[/+]on Nov 19, 2025
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: I don't think it is a regression. It looks like a case that hasn't been considered before
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Test:
Go to workspace chat
Create two duplicate manual expense
Open the expense thread > Review duplicate.> Keep all
Open one of the expenses > Right click on 'resolved the duplicate' message > Reply in thread
Verify that you see resolved the duplicate message on report header, LHN title
Click on the report header
Verify that you see resolved the duplicate message on report details page
Activity
melvin-bot commentedon Nov 15, 2025
Triggered auto assignment to @NicMendonca (
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.etCoderDysto commentedon Nov 15, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
Chat - You is displayed on chat header, and LHN when opening resolved duplicate messsage
What is the root cause of that problem?
We are not handling
CONST.REPORT.ACTIONS.TYPE.DISMISSED_VIOLATIONaction type ingetReportNameApp/src/libs/ReportUtils.ts
Lines 5724 to 5726 in ca4289f
What changes do you think we should make in order to solve the problem?
We should handle
CONST.REPORT.ACTIONS.TYPE.DISMISSED_VIOLATIONaction type ingetReportNameas we are doing forPureReportActionItemApp/src/pages/home/report/PureReportActionItem.tsx
Lines 1281 to 1282 in ca4289f
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
[-]Chat - You is displayed on chat header, and LHN when opening resolved duplicate messsage[/-][+][$250] Chat - You is displayed on chat header, and LHN when opening resolved duplicate messsage[/+]melvin-bot commentedon Nov 19, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021990961159543969561
melvin-bot commentedon Nov 19, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @DylanDylann (
External)DylanDylann commentedon Nov 20, 2025
@etCoderDysto's proposal looks good to me
🎀👀🎀 C+ reviewed
10 remaining items
etCoderDysto commentedon Nov 26, 2025
@DylanDylann PR is ready for review
melvin-bot commentedon Dec 20, 2025
This issue has not been updated in over 15 days. @NicMendonca, @mollfpr, @DylanDylann, @etCoderDysto eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
etCoderDysto commentedon Dec 20, 2025
@NicMendonca PR has been deployed to production 3 weeks ago. The issue is ready for payment ;)
DylanDylann commentedon Dec 20, 2025
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: I don't think it is a regression. It looks like a case that hasn't been considered before
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Test:
Do we agree 👍 or 👎
DylanDylann commentedon Jan 5, 2026
@NicMendonca Could you please handle the payment?
NicMendonca commentedon Jan 14, 2026
Payment Summary
Contributor: @etCoderDysto paid $250 via Upwork
Contributor+: @DylanDylann due $250 via NewDot
JmillsExpensify commentedon Jan 20, 2026
$250 approved for @DylanDylann