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-10-01] [$250] Export - "Exported to CSV" message appears on the expense report page, when one expense exported #70015
NOTE FIX required: Only add a system message to a report when the entire report (i.e. all expenses on it) is exported to a CSV and not when only some of the expenses are exported
Version Number: 9.2.2-0 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from TestRail:https://test-management.browserstack.com/projects/2219752/folder/13176922/test-cases/41237500 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Device used: macOS Sequoia 15.6 - Chrome App Component: Money Requests
Action Performed:
Sign in to ND
Navigate to the workspace chat, create two expenses
Navigate to the Reports tab/ Expenses
Select one of the expenses from the step 2, click on "1 selected" - Export - Basic export
Click Save
Navigate to the workspace chat, open the expense report, open the exported expense
Expected Result:
"Exported to CSV" system message appears on the expense details page, like when you hold one of the expenses, for example
Actual Result:
"Exported to CSV" system message appears on the expense report page under the list of expenses, when only one expense from the report was exported
@nlemma are you sure this is a bug? Given the export action occurs on the report rather than the expense, I think the behaviour you are seeing is expected but if you've been told otherwise, please let me know and I can look into it further
@nlemma to clarify, is this being raised as a bug because of the fact that only one expense on a report with multiple expenses is being exported and then the export system message is added to the report even though the whole report was not exported?
And the conclusion was that we should not be added a system message to the report in the event that the full report is not exported. And since the exported system message is a report level action, it isn't possible for it to be added to the individual expense.
So I agree this is a bug and the fix that needs to be implemented is to only add a system message to a report when the entire report (i.e. all expenses on it) are exported to a CSV.
@nlemma would that resolve the bug from your perspective?
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.17-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@truph01@heyjennahay 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:
[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.
Activity
melvin-bot commentedon Sep 6, 2025
Triggered auto assignment to @heyjennahay (
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.heyjennahay commentedon Sep 9, 2025
@nlemma are you sure this is a bug? Given the export action occurs on the report rather than the expense, I think the behaviour you are seeing is expected but if you've been told otherwise, please let me know and I can look into it further
nlemma commentedon Sep 9, 2025
@heyjennahay, the markdown format isn’t applied correctly yet, but here’s a snippet from the test case.
heyjennahay commentedon Sep 11, 2025
@nlemma to clarify, is this being raised as a bug because of the fact that only one expense on a report with multiple expenses is being exported and then the export system message is added to the report even though the whole report was not exported?
nlemma commentedon Sep 11, 2025
@heyjennahay Yes, that's correct.
heyjennahay commentedon Sep 11, 2025
Ok thanks for helping me understand. I'm going to take this to the project team to clarify and come back to you
heyjennahay commentedon Sep 12, 2025
Ok discussed this in Slack https://expensify.slack.com/archives/C07NMDKEFMH/p1757614917882899
And the conclusion was that we should not be added a system message to the report in the event that the full report is not exported. And since the exported system message is a report level action, it isn't possible for it to be added to the individual expense.
So I agree this is a bug and the fix that needs to be implemented is to only add a system message to a report when the entire report (i.e. all expenses on it) are exported to a CSV.
@nlemma would that resolve the bug from your perspective?
melvin-bot commentedon Sep 15, 2025
@heyjennahay Whoops! This issue is 2 days overdue. Let's get this updated quick!
27 remaining items
melvin-bot commentedon Sep 24, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.17-6 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-10-01. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Sep 24, 2025
@truph01 @heyjennahay 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]
heyjennahay commentedon Oct 3, 2025
@nkdengineer can you please complete the BugZero checklist so I can process payments?
truph01 commentedon Oct 6, 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:
[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: https://github.com/Expensify/Expensify/issues/554639
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
luacmartins commentedon Oct 6, 2025
Just pending payment
heyjennahay commentedon Oct 6, 2025
Confirmed that both jobs have been paid and closed in Upwork.
Thanks everyone!