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
[Due for payment 2025-11-26] [$250] Report - 'Comments' sub-header not shown in the chat #73686
Version Number: v9.2.39-2 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from BrowserStack:https://test-management.browserstack.com/projects/2219752/folder/13176730/test-cases/41237110 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Device used: Windows 11, Chrome App Component: Other
What changes do you think we should make in order to solve the problem?
We should bring the sub-header change back from here in MoneyRequestReportTotalSpend and only display it if the report has no transactions
Now we have Add expense button, then if we still want Comments sub-header. We need to update the UI accordingly and we can discuss about this with design team in the PR.
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
None
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 [-]Report - 'Comments' sub-header not shown in the chat[/-][+][$250] Report - 'Comments' sub-header not shown in the chat[/+]on Oct 29, 2025
changed the title [-][$250] Report - 'Comments' sub-header not shown in the chat[/-][+][Due for payment 2025-11-26] [$250] Report - 'Comments' sub-header not shown in the chat[/+]on Nov 19, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.59-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@suneox@kadiealexander The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
[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 think there won’t be any PR specifically responsible for this issue because the refactoring in PR fix: Add the "Add expense" button to two areas of the product. #71267 was primarily focused on adding "Add expense" button functionality to money request reports. During this process, the existing logic that displayed the "Comments" sub-header for reports containing chat messages was also removed on the UI mockup
[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: N/A
[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.
Activity
melvin-bot commentedon Oct 28, 2025
Triggered auto assignment to @kadiealexander (
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.nkdengineer commentedon Oct 28, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
The 'Comments' sub-header is missing in the chat view.
What is the root cause of that problem?
The
Commentssub-header is removed hereWhat changes do you think we should make in order to solve the problem?
We should bring the sub-header change back from here in
MoneyRequestReportTotalSpendand only display it if the report has no transactionsNow we have
Add expensebutton, then if we still wantCommentssub-header. We need to update the UI accordingly and we can discuss about this with design team in the PR.What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
None
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.
melvin-bot commentedon Oct 29, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021983395431269974507
[-]Report - 'Comments' sub-header not shown in the chat[/-][+][$250] Report - 'Comments' sub-header not shown in the chat[/+]melvin-bot commentedon Oct 29, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @suneox (
External)suneox commentedon Oct 30, 2025
Proposal from @nkdengineer LGTM
🎀 👀 🎀 C+ reviewed
14 remaining items
[-][$250] Report - 'Comments' sub-header not shown in the chat[/-][+][Due for payment 2025-11-26] [$250] Report - 'Comments' sub-header not shown in the chat[/+]melvin-bot commentedon Nov 19, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Nov 19, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.59-5 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 2025-11-26. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Nov 19, 2025
@suneox @kadiealexander The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
suneox commentedon Nov 25, 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 think there won’t be any PR specifically responsible for this issue because the refactoring in PR fix: Add the "Add expense" button to two areas of the product. #71267 was primarily focused on adding "Add expense" button functionality to money request reports. During this process, the existing logic that displayed the "Comments" sub-header for reports containing chat messages was also removed on the UI mockup
[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: N/A
[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.
N/A: It isn't an impactful bug
kadiealexander commentedon Nov 28, 2025
Payment Summary
garrettmknight commentedon Dec 18, 2025
$250 approved for @suneox
twisterdotcom commentedon Mar 11, 2026
@nkdengineer has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-b177-a65d-8a38-27301fe63ba4